When we detect something wrong with your site (it is down, a broken link is detected, the certificate is invalid, ...), we can notify you via one of the many notification channels we support. One of those channels is Pushover, an excellent service to send native notifications to mobile devices. We have supported Pushover since we launched a couple of years ago. Now, we've added a nice option that several of our users we're asking for: setting the priority.

Your engineers probably dislike going on-call for your services. Some might even dread it. It doesn't have to be this way. With a few changes to how your team runs on-call, and deals with recurring alerts, you might find your team starting to enjoy it (as unimaginable as that sounds). I wrote this article as a follow-up to Getting over on-call anxiety.

A selection of questions and answers from our recent webinar on leveraging AIOps to run sustainable, blameless retrospectives.

Murphy’s Law states that anything that can go wrong, will go wrong. The challenge for most businesses is putting the right method of communication in place for when the inevitable happens. The only way to handle this is to expect the worst and then prepare for it. A key factor in deciding for any alerting solution is can my team be notified properly when a major outage happens .

As soon as the ITOps technician is ready to grab a cup of coffee, a zing comes along as an alert. Cling after zing, the technician has to respond to so many alerts leading to fatigue. The question is why can’t systems be smart enough to predict bugs and fix them before sending an alert to them. And, imagine what happens when these ITOps personnel have to work with a complex and hybrid cloud of IT systems and applications. They will dive into alert fatigue.

This post covers some of the highlights that we have released in the last 6 months.