Showing results for 
Show  only  | Search instead for 
Did you mean: 

Release monitoring for several deploys on same JBoss instance


Hello community,

I'm currently working on implementing release version tracking with Dynatrace for our applications running on JBoss. However, we have multiple deployments running on the same JBoss server, and I'm looking for the best approach to identify and differentiate these deployments in the releases view.

Specifically, I'd like to know how to:

  1. Tag or label each deployment to recognize it.
  2. Associate a version or release number with each deployment.
  3. Ensure that the monitoring system correctly tracks and reports on these individual deployments.

Any insights, best practices, or recommendations on how to achieve this would be greatly appreciated. 

thank you all!


DynaMight Guru
DynaMight Guru

Hi @gbeltramelli1 

Here you will find the necessary information on how to mark your implementations:

  • DT_RELEASE_VERSION for Version
  • DT_RELEASE_STAGE for Stage
  • DT_RELEASE_PRODUCT for Product
  • DT_RELEASE_BUILD_VERSION for Build version

Here you find details about a release:




Have a nice day!

Thank you so much for your time! 

As far as I understand about all the documentation it's not possible to do what I need.

Remember that I have several deploys in same jboss instance / process so environment variables are going to affect all my deploys with out distinction. 

Is there any other way that it with out environment vars? 

That's what I am running into as well. It wants the as environment variables which are global on that server and not in relationship to each API/service.

However there is a way to push an event to Dynatrace to record a new event. This could be a release/version update. I am looking into this path or updating a Tag in Dynatrace for each API as part of the CD cycle via API.


Yes you can push an event but you will be missing the release inventory, unfortunately as this lack of functionality or properly documentation, our devops teams opt for a different solution so we will no longer use this dynatrace function. 


I'm facing the same kind of lack.

We are running two different tomcat instance on the same server and exporting global envirronment variables will make both instances share the same RELEASE info which is not the case.


Is there a way to do this properly now ? 

Featured Posts