A while ago, I wrote about how we track on-call health, and I heard from various people about how “expecting to be woken up” can be extremely unhealthy, or how tracking the number of disruptions would actually be useful. I took that feedback to heart and wanted to address the issues they raised, and also provide some numbers that explain the position I took with these metrics on alerts.
We are happy to announce today that we have launched further improvements to the Logit.io platform’s alerting and monitoring features. This latest release of the Logit.io platform offers our users an improved workflow to assist with their productivity on the platform as well as a more updated intuitive user interface (UI).
Unless you stare at Sentry all day waiting for error or performance problems to pop up, chances are you rely on alerts to let you know when something breaks or slows down. There are two types of alerts you can set up: 1) Issue Alerts, which are tied to issues that meet predefined criteria, and 2) Metric Alerts, which trigger when error volume or performance metrics like apdex, latency, or throughput surpass a pre-defined threshold.
This post highlights some of the features and improvements that we have released in the last 3 months. If you want to submit your own ideas or vote on existing feature requests, you can now use our new public roadmap at roadmap.ilert.com.
With cybersecurity boundaries going beyond the traditional walls of an office and attack surfaces constantly expanding, data breaches are inevitable. Managing risks from data breaches requires organizations to develop a comprehensive incident response plan – an established guideline that facilitates incident detection, response and containment, and empowers cybersecurity analysts to secure a company’s digital asset.
