topic Problem alerting profile issue in Alerting

Problem alerting profile issue

kobkob — Wed, 27 Nov 2024 08:03:24 GMT

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.

Re: Problem alerting profile issue

AntonPineiro — Tue, 26 Nov 2024 14:11:56 GMT

Hi,

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

Best regards

Re: Problem alerting profile issue

kobkob — Tue, 26 Nov 2024 14:22:11 GMT

@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.

Re: Problem alerting profile issue

AntonPineiro — Tue, 26 Nov 2024 17:38:12 GMT

Hi,

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

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

Best regards

Re: Problem alerting profile issue

kobkob — Tue, 26 Nov 2024 19:03:09 GMT

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

Re: Problem alerting profile issue

Peter_Youssef — Wed, 27 Nov 2024 09:10:13 GMT

Hello @kobkob

In addition to the suggestion provided by @AntonPineiro , PFA Resources for resolution:

Hoping it adds value,

BR,

Peter