We are heavy users of your platform an rely on the site24x7-StatusIQ integration to update our public facing status page. Our app will occasionally have a 1-2 minute service blip and when that happens, StatusIQ is updated to "Major Outage"" and hundreds or thousands of emails go out to customers. It looks REALLY bad and at this point our leadership requires a fix which could mean having to move away from site24x7 unfortunately. We would like to delay the status page update for these occasional service blips. In other words, the monitor must fail n-number of times before the status is updated.
This can be implemented in several places...
Site24x7 - Under "Threshold and Availability" policy there's currently a downtime rule called "Number of locations to report monitor as down". An additional option here labeled "Number of attempts to report monitor as down" would work.
Site24x7 - Similar to the "Notification Profile", have another profile called "Status Page Profile" where the downtime can be delayed similar to the way the Notification Profile works.
StatusIQ - In the component properties, an option labeled "Number of status check failures required before marking component as down"
Based on what I know about the site24x7-StatusIQ integration, it seems one of the first two options would be easiest to implement but however you can do it is fine with me.
Dear Russell,
Thank you for stating the problem and suggesting a solution as well. We will check and this and provide a solution.
-Jasper
Site24x7, PM
We need this as well - it would be an awesome nice feature, and it will provide better end customer communication
Dear Folks,
Thanks for your sharing your thoughts. To give some clarity on this feature, StatusIQ doesn't take into account the Notification Profile settings when the monitor's status change. If the monitor is mapped to StatusIQ as a component and the monitor's status changes we will create the incident or update the incident (based on the settings in StatusIQ > Admin > Status Automation) directly.
Henceforth, we plan to honor the Notification Profile set in monitor and based on that StatusIQ's status will be updated. Which means if for example in Notification Profile, the Downtime notification Delay is "Notify after 5 continuous failures", status will be updated as many polls.
We may consider other options to further delay the status update after internal discussion.
Please let us know your feedback on this.
-Jasper
PM, Site24x7
This is great. Thank you Jasper.
I feel this is a good solution. If you'd like to make it a great solution, a separate delay setting for status page update would be even better because we can get notification that there's a potential system problem immediately but not update the Status page for a couple min. That will give us a head start on determining the issue and may give us enough time to even do something such as a reboot of services (whether by automation or manually).
If you use the same notification profile for both notification and status page updating, our workaround for now would be to create two monitors for the same endpoint; one that notifies immediately but NOT tied to a status page component and another monitor that delays notification which IS tied to a status page component. It's not as optimal but would suffice.
Hi Rusell / Facundo / Torsten,
We have supported this in our recent release. Now Site24x7 Notification Profile will be considered while pushing monitor status to StatusIQ from Site24x7.
For example, for a Site24x7 monitor if "Notify after five continuous failures" is configured in its Notification Profile, then status will be pushed to StatusIQ only if monitor is found down 5 times continuously.
You can check other Site24x7 status automation enhancements we supported and few other important features which we added to StatusIQ in our recent releases in this post - https://www.site24x7.com/community/introducing-new-ways-to-share-and-customize-your-status-pages.
Thanks
Laxmikanth