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

Problem alerting profile issue

kobkob
Contributor

Hi community,

 

I have an issue while problem that based on metric event I created is opened.

The metric event type is metric selector that follows response time on the *service* level (entitySelector("type(service)).

The dimension ket of entity events is also *service*.

When a problem is opened and the affected entities are service *and* host, all the alerting profiles in the *host* also attached to the problem. 

I tried to filter it by adding a tag called "service" to all of the services and a rule to the alerting profile that says "only include entities that have all tags" and the relevant tag and the "service" tag (which of course the host doesnt have the "service" tag") but it didnt work.

Any ideas?

 

Thanks in advance.

5 REPLIES 5

AntonPineiro
DynaMight Guru
DynaMight Guru

Hi,

Can you define another dimension in metric event? What do you try to achieve with that metric event?

Best regards

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

@AntonPineiro No, I can only add "property" which I'm not sure what is that.

I'm just trying to open a specific problem on the service level, and it works, but the issue is with the alerting profile attached.

Hi,

You can add a property to metric event, and create some negate condition in alerting profile base on that property.

  1. Adding property "X" to metric event.
  2. Adding negate property filter in alerting profiles.

Best regards

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

@AntonPineiro Sure, but the question is what. Can you give an example?

Dynatrace Davis® AI automatically analyzes and alerts abnormal situations within your dynamic IT infrastructure and attempts to identify any relevant impact and root cause. But every business works differently and you might want to use the power of Davis to configure anomaly detection on your ...

Featured Posts