Splunk Completes Acquisition of Plumbr Learn more

Identifying applications

To distinguish between applications, the application identifier is set in the Plumbr Agent configuration. It can also be changed via the Plumbr user interface available at https://app.plumbr.io. In essence, it is just a string, uniquely identifying each software bundle you wish to monitor with Plumbr.

The configuration determining the application is different for the web applications monitored by Browser Agent and APIs running in server-side:

For web applications monitored by Plumbr Browser Agent, application is specified as a parameter to the Browser Agent installation as seen in the following example via appName parameter:

<script src="https://browser.plumbr.io/pa.js"

For server-side APIs monitored by Plumbr Java Agent, application name is derived from two properties specified in Java Agent configuration located in plumbr.properties file.

You will find these properties from the plumbr.properties file next to the Agent’s plumbr.jar file:

  • jvmId. Specify this parameter for JVMs which survive restarts. They can also be permanent members of clusters. jvmId is unique and cannot be reused by several JVMs.
  • clusterId. Specify this property if the JVM monitored by Plumbr is either a member in load-balanced cluster or an ephemeral node with short lifecycle. This way all the members sharing the same clusterId exposing the same API end up aggregated under the same cluster.

Specifying at least one of these attributes is mandatory.

To give you an idea, some examples of typical application names we see include:

  • CRM
  • eShop
  • Order Management


  • eshop-test
  • eshop-staging
  • eshop-production

Feel free to pick any string uniquely identifying the application. Pay attention that it helps if the rest of the team can associate the name later with the real software, so names as “kate experimenting” or “second application” tend not to be good choices.