17 Jan 2024 12:23 PM - edited 17 Jan 2024 03:42 PM
⚠️ If you haven't created an alerting profile yet, please read the steps provided in the documentation. Link here.
In some situations, we expect an alerting profile to detect a problem, but it doesn't. In this troubleshooting post, we're going to review the top main causes.
If the Alerting profile was created or enabled when the problem was already open, you aren't going to see the desired Alerting profile on that problem.
We will have to consider two things:
3. Once we click, we can see Revision History. In there, we have an overview with different information regarding the changes that have been applied:
At the top left corner, the ID of the alerting profile is shown. Then, we will see a new row every time we make a modification regarding our profile. In each of the changes, we can see when it was made, what type of change it is, and what the original and new values of the recent changes were. If we switch to advanced mode, we can compare everything we had before with the new values in a detailed way.
Suppose we have an Entity "A" with management zone "X":
Sometimes, when a problem is created, the impacted entity doesn't have the X for different reasons when we expect to see it in A.
Usually, we see that A doesn't have X due to a problem related to the management zone rule. We recommend checking the following in management zone settings:
That is why it is important to check step number two, as it is crucial to verify if the rule applies to any entity we have in our environment.
If you're using event filters, you need to verify how they are configured. Here you can see some typical problems we see with event filters:
2. For metric events, it would be necessary to use the custom filter. Below, you can see how it looks like the custom filter works. You can use, for example, a title filter, but there are other options like description or property filters.