topic Re: "Impacted" attribute in metric events with metric selector in Open Q&A

"Impacted" attribute in metric events with metric selector

Theodore_x86 — Fri, 09 May 2025 14:46:21 GMT

Hello.

I am interested knowing how Dynatrace determines the Impacted entity when a metric selector is used.

I noticed problems with impacted entity the whole environment, meaning that Davis did not understood the exact entity that the problem corresponds to.

Thank you.

Re: "Impacted" attribute in metric events with metric selector

marco_irmer — Fri, 09 May 2025 22:31:59 GMT

The metric event has to be configured with a dimension key to tell it where to find the entity that the event should be associated to.

Once that is done, the Davis Event (and resulting problem) should be associated with the appropriate entity.

Re: "Impacted" attribute in metric events with metric selector

Theodore_x86 — Fri, 09 May 2025 22:52:44 GMT

Hello.

That was my initial thought as well, however I noticed problems with the dimension key set to Automatic but with proper relation to the monitored entity. In other cases though the related entity was the Environment.

My second guess is that the metric selector exception should have a "split by" dimension defined and not just the "split by()", hence a NULL value inside the parenthesis.

I am not 100% certain though.

Re: "Impacted" attribute in metric events with metric selector

Nick-Montana — Mon, 12 May 2025 13:20:16 GMT

What metric are you attempting to create an event off of? Custom or built-in?

If its a custom you can set additional metric metadata on the metric itself that may improve the results you're attempting to observe:

https://docs.dynatrace.com/docs/ingest-from/extend-dynatrace/extend-metrics/reference/custom-metric-metadata#metric-parameters--example-json