Delay alert / Trigger incident after specific number of failures (No immediate downtime)#703
Is there a possibility of adding an option where it will only trigger a downtime event after 2 or more timeouts/error codes are detected?
For example I use many port monitors and occasionally I get a random timeout even with 1 minute set for it. If I could set it to only trigger a downtime event after 2 or more timeouts I feel that would help cut out some potential false triggers.
Hi there. Setting up a delay in notifications wouldn’t solve your issue? head over the “cog icon” next to alert contact to find out.
Hi folks, there are quite a lot of requests regarding triggering incidents / alerting after a certain number of failed attempts. Many of these requests share a similar message, although we have noticed some differences as well. That’s why we’re asking these questions to make things as clear as possible in order to provide the best possible solution:
These are the two main feature requests we’ve seen:
- Delay notifications when an incident occurs
- Delay incident creation
Did you know you can use “Delay and recurrence settings” or “Advanced notification settings” in each monitor for a specific alert contact (any email, sms contact, integration..)? In doing so, you can set up a delay for a specific number of minutes. E.g. you will get alerted for the first time only 5 minutes after the incident starts (the incident is created immediately). In other words, if the incident is shorter than 5 minutes, you will not get alerted at all. Does this feature solve your problem? Considering the fact that we are doing 1-minute checks once the downtime occurs, the “Delay for 5 minutes” means the same as “Delay for 5 failed attempts”. So, in short, this feature already exists. It is available for all paying customers in the advanced notification setting.
With this in mind, I think we can close this suggestion and move on to “Trigger incident only after X minutes”?
This seems quite similar, with the main difference being that we won’t even create an incident if the incident is shorter than X minutes, so it does not affect your stats. Is this the reason you are asking for this feature?Another valid point would be that need to setup this once per monitor, not per monitor per alert contact.
As always, we want to offer you the best service possible, so let us know what you think!
Yes, once pee monitor is ideal. Per contact is useless as the point is setting this unique value per system being monitored. Bulk actions to apply are always nice though.
Hy