Go to All Forums

Expanding Sustained Alerting

My understanding from the Site24x7 support staff is sustained alerting for URL monitors is limited to the page response monitors (illustration below). It would be more useful to provide sustained alerting for all URL monitors (e.g.: HTTP 400 and above, DNS, socket timeout, etc.). This would allow automation to filter through valid alerts while ignoring insignificant, short term blips. I previously used a five minute sustained "observation" mode with a competitor's product. That worked quite well, ensuring only valid alerts were actioned. I'd love to see a high caliber product like Site24x7 be more helpful on this front.


Like (2) Reply
Replies (5)

 
Hi Alan,
 
Thank you for raising your query.
 
For cases like HTTP 400 and above, DNS failures, or socket timeouts, Site24x7 treats these as a Down status. You can configure automation for such errors directly from the monitor’s edit page under the Configuration Profiles section.
 
 
If you’d like to delay notification alerts, you can use the Notification Delay option available under the Notification Profile in the monitor's edit page Alert settings section.
 
 
 Feel free to contact us if you need more help.
 
Regards,
Jenzo
Site24x7
 
 
Like (0) Reply

Hi Jenzo, 

Thanks for your reply. The lone IT automation for website monitors is Invoke URL/REST API. That appears to be limited to creating a webhook. How does a webhook equate to suppressing alerts until a sustained period of time is breached? 

I'm aware of the notification delay option. But without the above alert delay option, my objective wouldn't be achieved.

Can you please elaborate on how to setup sustained alerting? This would apply to the rest of the website monitors - similar to that which is available for the page response monitors. 

For reference, here's a snippet of how I accomplished that in my previous web monitoring tool. One simple setting covered the various URL monitors:

Like (0) Reply

To further illustrate my feature request need, here's a recent example of a 504 that lasted little over one minute and then vanished without return. I want to eliminate receiving alerts for these types of blips (false alarms) by using a five minutes sustained suppression. Anything persisting post five minutes would warrant investigation and should alert only at that point.

Like (0) Reply

 
Hi Alan,
 
We would like to inform you that we understand your perspective on including additional attributes such as HTTP 400 and above, DNS, socket timeout, etc, beyond just response time for the poll strategy for monitors. 
 
We truly value your feedback and will work towards incorporating these as enhancements in our upcoming updates.
 
Regards,
Jenzo
Site24x7
Like (0) Reply

That would be superb!

Like (0) Reply

Was this post helpful?