03 Mar 2025 03:48 PM - edited 03 Mar 2025 07:42 PM
I tried searching to see if anyone else had identified the entity selectors needed to add ElasticSearch data to a Management Zone. I didn't find anything in the first few minutes of looking but I did find this : Solved: Add extensions to a Management Zone - Dynatrace Community and @Mike_L post on finding the relationships. I used this as a starting point, and got this for ElasticSearch
I started by adding a tag App:XYZ to the Elastic Search Cluster Node. This will allow me to select a particular cluster to add to the Management zone and have all the other underlying parameters added via relationships.
I then added the following rules to the Management Zone
type("elasticsearch:cluster"),tag("App:XYZ")
type("elasticsearch:index"),fromRelationship.runsOn(type("elasticsearch:cluster"),tag("App:XYZ"))
type("elasticsearch:disk"),fromRelationship.isChildOf(type("elasticsearch:node"),fromRelationship.isChildOf(type("elasticsearch:cluster"),tag("App:XYZ")))
type("elasticsearch:node"),fromRelationship.isChildOf(type("elasticsearch:cluster"),tag("App:XYZ"))
type("elasticsearch:thread_pool"),fromRelationship.runsOn(type("elasticsearch:node"),fromRelationship.isChildOf(type("elasticsearch:cluster"),tag("App:XYZ")))
The only one I didn't add from the first screenshot was elasticsearch:node is same as host, because the node was already added in a different rule. I'm not 100% sure this is correct, however when navigating the extension data in and out of the management zone, I could not see any difference. However if anyone has any thoughts on that, or if I missed anything, please add.
Note this was done on Dynatrace Managed, 1.306.93
03 Mar 2025 08:57 PM
Thanks! Helpful as I used to tie AWS accounts to only needed metrics based off tags