Monitoring Alerts

6 steps to IT alerting best practices

Not all alerts are created equal

Even though most IT teams have adopted IT alerting practices, they are often far from monitoring and alerting best practices. It’s not enough to just have an alerting tool. Like a monitoring tool, if left uncalibrated, alerts will simply produce a sea of noisy data. Instead, teams should calibrate alerts so that they are meaningful.

For example, a meaningful alert might be something along the line of web requests are taking more than x seconds to process and respond or new servers are failing to spin up as expected. And these are great examples of what could be high priority alerts for a company.

Alternatively, alerts that are less high priority, such as server is 90% full can be a low priority alert that can be forwarded to the on call engineer but don’t rise to the level of a 2am wakeup call. In OnPage, you can send this low priority alert to go to the engineer’s account but ensure the account notifies the engineer during normal business hours.

6 steps to IT monitoring and alerting best practices

It’s an important realization that not all alerting needs to wake up an engineer. The trick to successful alerting is to provide meaningful alerts when issues do occur. To this end, OnPage has the following alerting best practices which have been vetted by our numerous end users:

  • Make sure your alerts are calibrated. Establish a baseline so you know how your systems are supposed to work
  • Ensure alerts are tied to a schedule. As weird as it sounds, some shops just alert everyone. You never want to alert everyone. Make sure your alerts are tied to a schedule so that one person is alerted. If the engineer is unavailable, then escalate to the next person on call.
  • Ensure alerts are actionable. Who wants to be woken up to a message that is pointless such as there’s a problem with deployment in the test environment. Instead, ensure alerts have a direct piece of information that needs to be investigated and resolved.
  • Develop run books. Publish operating procedures so on-call can become more standardized.
  • Review audit trails. Make sure alerts went to the right person on the team who is best able to resolve the issue
  • Review on call at weekly meetings. Review alerts that were received during the week to ensure sufficient information is arriving with alerts and that alerts are actionable. If they are not, then alter the alert messaging so it is more effective.

By following these steps your team will begin the process towards thinking from a proactive rather than a reactive position.

For more information…

 

OnPage Corporation

Share
Published by
OnPage Corporation

Recent Posts

Top 12 AI and LLM Observability Tools in 2026 Compared: Open-Source and Paid

Artificial intelligence has moved far beyond experimentation. In 2026, AI systems are embedded into customer…

3 days ago

What are the MOST Promising and High-Demand IT Jobs Right Now

Jobs in the technological sector have been shrinking. The Chief Economist at Glassdoor states that in the…

7 days ago

From Passive Records to Active Care: Activating the EHR in Real time in Israel’s hospitals

Israel’s healthcare system is widely recognized as one of the most digitally advanced in the…

1 week ago

Platform Engineering 101: What It Is, How It Differs from SRE and DevOps, & Why It Matters for Incident Response

Platform engineering has emerged as a response to the growing complexity of modern software delivery.…

2 weeks ago

AI Is Changing Healthcare Faster Than Most Systems Are Ready For

(My key takeaways from a clinician-led roundtable on AI, access, and care delivery) Healthcare is…

3 weeks ago

Silent Failure in Production ML: Why the Most Dangerous Model Bugs don’t Throw Errors

You've done it. Your machine learning model is live in production. It's serving predictions, powering…

4 weeks ago