Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



At StatusCake we’ve got a great range of integrations for alerting, today we want to take you through some of the advantages of using OpsGenie which differs from some of our other integrations in that it has several extra layers of setup beyond what can be configured in the StatusCake app.
With the StatusCake-OpsGenie integration, it’s easy to set up your different teams or individual staff under their own on call schedules. These can be set up on daily, weekly, or custom rotations, and this allows for advanced scheduling scenarios like after hours, weekdays and weekends, or even teams based in different geographical locations. There’s also a handy tool called “Schedule Previewer” which allows you to instantly get an overview of your set up in this regard.
For every alert sent from StatusCake through OpsGenie, you will be able to view detailed tracking information. Within the OpsGenie activity log, you can see when the alert was created and sent, who was notified, the time at which the alert was picked up by the recipients, and any logged action that has been taken.
As well as notifying multiple users at the same time, StatusCake alerts through OpsGenie can have escalation policies applied to them. This means that if the first team or individual to receive the alert does not pick it up for a set time frame the notification can then be forwarded on to another team, you can set this up to alert different staff/teams in order until the problem is resolved.
With the OpsGenie app installed on a mobile device, it’s possible for staff to take appropriate actions in response to alerts that they receive. A set of default actions such as closing the alert and adding a note are available from the app from the get-go, and custom actions can also be added to suit your team’s needs.
Another great function available through the StatusCake-OpsGenie integration is the ability to parse incoming alerts from StatusCake, this means not just that they can always go to the right person with the right information, but also that you can choose to convert the type of alert that’s sent. When a StatusCake alert hits your OpsGenie dashboard it can then be automatically converted to an alert in Email, SMS, Mobile Push, or Phone Call format.
If you already use OpsGenie, or if you were considering giving it a try you can view the set up guide here – if you have any questions just get in touch with our friendly support team who will be happy to help!
Share this
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
Find out everything you need to know in our new uptime monitoring whitepaper 2021