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

This product reached the end of support date on March 31, 2021.

Need JVM agents to appear in more than one system profile


I'm not sure if this is the correct way to go about this but here's my issue. I have 3 system profiles containing application groups. Let's call them "Big Cluster 1", "Big Cluster 2", and "Product Catalog"

Both "Big Cluster 1" and "Big Cluster 2" contain Pure Paths and transactions that call the "Product Catalog". Unfortunately what seems to happen is that when a transaction starts in the "Big Cluster 1" system profile it is no longer visible or searchable in the "Product Catalog" system profile, I'm assuming to prevent lots of duplication?

If this were a case where ONLY Big Cluster 1 called Product catalog, I would simple move the JVMs from the Product Catalog profile over to the Big Cluster 1 profile, so that all transactions were searchable all the time regardless of where the transaction starts. The problem is that Big Cluster 2 also calls the Product Catalog.

Is there any way I can add the JVM agents from the Product Catalog to both of the Big Clusters? Would this blow up my Collector with too much duplication? Is there a better way to go about this that I'm not thinking of? Any help would be appreciated!


Dynatrace Pro
Dynatrace Pro

Hi Jeff,

This topic of "Cross-Profile PurePaths", where one system profile (Big Cluster 1) "steals" the PP that you expect to see in another profile (Product Catalog) is a long-known situation in the product. While work is being done to address this and provide better control over the situation in future releases of the product, the configuration that you have now is technically unsupported. The rule in every version up to the current 6.x is that "any agents that you are monitoring on a single dT server that call each other must be in the same single System Profile". So technically you should have just one SP that monitors all of BC1, BC2, and PC. You could then differentiate those apps using the Application feature of the product.

If you truly want to have 3 SPs, where each SP reflects all (and only) its own PPs, you can make that work, and I've done this at various customers. What you would need to do is stand up a second dT server, and use that to monitor your Product Catalog, with a single PC system profile. You would leave both of BC1 and BC2 on the current server, each with its own SP. Now in each of BC1 and BC2 you will see the API calls to PC, including how much time is spent in each call, but it won't continue into the PC code. On the second dT server, you'll have PC PurePaths reflecting the calls made by BC1 and BC2. This works well, and generally reflects the group structure of most teams, where different people maintain the code for the app (BC1) and the common services (PC).

Hope this helps,



I totally agree with Rob, It'd be ideal to have all the agents in one single profile, and then separate Views for the desired Application.

It seems like there are dependencies/calls/ if you have all of them under one single SP you will make sure you have every single PurePath, based on my humble opinion.

I do have quite a few customers with that set up, working well for over 4 years now.

Hope this helps,


Thank you for the information, that was super helpful!