Application versions

Whenever you release a new version of your application, you can let Plumbr know about it as well. Then Plumbr will be able to show you how the availability and performance metrics change across different versions of your application.

Application version is any string that uniquely and meaningfully identifies and distinguishes any given deployment from the previous one, e.g. “20.02.21” or “4.2.56” or “1.2-b45hfdf3”. We don’t impose any constraint on version identifier format or what exactly “version” means in your case.

You pass application version as one of the configuration parameter to Plumbr Agent. All our agents (JVM, Universal and Browser) accept this configuration parameter and annotate any collected data with its value.

Example 1

When running JVM application, the easiest way to pass version information is via environment variable:

export VERSION=4.3.18
export PLUMBR_APP_VERSION=${VERSION}
java -jar myapp-${VERSION}.jar

The similar approach works well with Docker-based applications:

export VERSION=4.3.18
docker run -e PLUMBR_APP_VERSION=$VERSION -d org.example/myApplication:$VERSION

Example 2

In case of web applications, it makes sense to inject application version together with the rest of Plumbr Browser Agent configuration during build time. E.g. when using webpack:

<script src="https://browser.plumbr.io/pa.js" crossorigin="anonymous"
    data-plumbr='{
        "accountId":"...",
        "appName":"...",
        "serverUrl":"https://bdr.plumbr.io"
        "appVersion": "<%= htmlWebpackPlugin.options.appVersion %>"
    }'>
</script>

Then pass version information during the build:

npm run build -- --appVersion 4.3.18