CPU Saturation Events

[sundarv1]

For CPU Saturation events, how do we create only problems and but not incident. 

[Ahmedrahbi]

Hi Sundarv, do you mean:

• You don’t want to receive any alerts or external notifications (like email, ServiceNow, etc.)?
  OR

• You don’t want the issue to appear in the Dynatrace UI under the Problems section at all?

[sundarv1]

We want the issue to appear only in problem section, but not as incident or email.

[AntonPineiro]

Hi,

You need to be sure you do not have any alerting profile matching that CPU event (with problem notification enabled).

Best regards

[sundarv1]

Hi AntonPineiro 

we have alerting profile matching that CPU event, question is out of 150 servers, we want only one server - we want only problem to be created, for rest problem and incident needs to be created.

[p_devulapalli]

@sundarv1 Depending on the way you have your alerting profiles setup, you can also use the event filters in combination with tags to filter out the CPU alerts for a specific host 

[sundarv1]

How do we use tag in the alerting profiles. I don't see an option there.

1. How do we negate option only for one host in defaullt alerting profile.

2. How do we use TAG in defaullt alerting profile.

[Aymeric_M]

Tags are available in the severity rules section of the alerting profile.
If you want the alerting profile to only match CPU events on 149 servers out of 150 you need to add a tag to those 149 servers and then on the alerting profile, in the Resources severity rule select "Only includes entities that have all tags" and set the same tag you just put on the 149 servers.