Getting started
⚠️ 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.
Alerting profile created or enabled when the problem is already open
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:
- When was the problem opened on the problems page? We will have to review the time the problem was reported on the problems page.
- When was the Alerting profile created or enabled? We can check that using Revision History on the settings of the Alerting profile. In order to review this, you'll need to follow the next step:
- First, we will need to go to our alerting profile.
- In the configuration of our alerting profile, we need to select the button located in the top right corner of the Alerting profile configuration, as you can see in the following image:
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.
The impacted entity didn't have the management zone defined in the Alerting profile when the problem occurred
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:
- Check recent revision history changes ( steps explained above ) to see if any user has modified any condition/rule/filter.
- Check if the rule applies to the entity where the problem is occurring.
- In order we just have to have two options:
- Use the button Preview for Conditions. This option will check if there is any entity that applies for that particular condition.
- Use the button Display entities. This option will check if there is any entity for all the conditions that we have created.
- In order we just have to have two options:
- If you're using Monitored entity, check the conditions you have added to the rule. For example:
- If you're applying the rule to "Host tag" with the name "production" and in the condition, we can see you're applying the rule to tags with the name "production. " As you can see, there is a blank in the end, so this condition will never be applied. We can see this happening many times with host names, tags, process group names, etc.
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.
Event filters
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:
- Custom filters don't match any predefined events. In the following image, we can see what a predefined event filter looks like. In order to capture predefined events, we need to use this kind of filter. Any other custom event can not be captured by this type of filter.
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.
