Is it possible to tag on JMX Editor metrics?

[larry_roberts]

I have a few teams starting to use the JMX Editor which is really nice, but I am stuck scratching my head a bit on how I can separate some things with auto-tagging. I had our first problem appear today from of the JMX Editor metrics which is looking at a simple message count.

But, here is where my problem comes in.

This is on a WebLogic 12.2 Admin Server. Our team is responsible for ensuring that WebLogic is running like clockwork and Dynatrace (SaaS) has been tagging it correctly with our team name as we have an auto-tag rule that states "Hosts where Host name contains 'wlssitadmin'". However, this other team which is called BackOffice is using the JMX Editor to pull some metrics from that same server for message count. That in return had a problem today, but our team (IT.ApplicationServices) was auto-tagged to it. Which I get, it's due to the rule above. So I thought it would be as simple as going back into the auto-tagging rules for our team and adding some sort of condition to exclude these JMX Metrics from our rules and to add them to the BackOffice auto-tagging rules.

The problem is... I can not for the life of me find any way to do this with auto-tagging. No matter what I select, I can find no way to see the JMX Metrics from the JMX Editor within the list to do anything like for example...

"Plugin name contains..." or "JMX custom metric name equals...." or anything like that. So essentially, I can find no way of separating specific things to one team or another through auto-tagging with the JMX Editor it appears.

I am really hoping I am just missing something here and not doing something correctly. I have tried for the past 2 hours to try to figure out a way to auto-tag the metrics coming out of the JMX Editor with 0% luck. Is this even possible? Am I maybe just doing something wrong?

Thanks in advance!

[Julius_Loman · Accepted solution]

Tags can be associated only with hosts / processes (process groups) / services or applications. They cannot be applied to individual metrics.
JMX metrics are assigned to the process they are being collected from.

[larry_roberts]

I had a feeling that might be the case from what I was seeing. Looks like my best way around it will be to use host groups and setup custom process groups. Thanks!