Smarter HTTP & Ping Monitoring
HTTP monitoring now only processes results when the status actually changes. If the status stays the same, the system skips unnecessary work.
Published: Monday, 01 September 2025
HTTP monitoring now only processes results when the status actually changes. If the status stays the same, the system skips unnecessary work. This improves performance, reduces noise from duplicate alerts, and prevents unnecessary incident creation. If you close an incident manually and the status has not changed, the system will not create a new incident for the same issue. This helps you stay focused on real changes, reduces unnecessary noise, and keeps incident management cleaner.
More updates
-
Labels for Teams
They are handy for larger organizations if you want to organize your teams into categories, e.g. departments or business units. You can also use them to filter your incidents or integrations.
-
Update/Patch Incidents via Outbound Webhooks
🚨 “Wait, why is our system still out of sync?” When incidents are mirrored across tools but updates don’t flow back automatically, you end up with version conflicts, duplicate work, and stakeholder confusion.
Product
Solutions
Compare
Resources