Tara Calihman October 06, 2015
Over the past few weeks, we’ve been working closely with the StatusPage team on something special. We’re really excited to announce the release of a new first-party integration! Now you’ll be able to post new incidents and update the statuses of your components without ever having to leave the VictorOps interface. We believe that the last thing you should be worrying about while firefighting is outage communication.
Let’s take a look at how it works…
(This is cross-posted from the StatusPage blog.)
One problem that DevOps teams face when dealing with downtime incidents is a flood of inbound questions from other employees at the company. The CEO wants to know why the site is down. The support team wants to know what to tell customers. The sales team wants to know when they can resume doing demos. It’s a nightmare.
They need to be focusing on fixing the actual problem, but instead they’re having to answer emails, phone calls, and people “just stopping by to see what the deal is”.
Enter the internal status page. Similar to how a public status page helps support teams mitigate support requests from customers, internal status pages help devops teams deflect inbound requests from employees.
Integrating with VictorOps was a no-brainer. VictorOps is one of the leading real-time incident management solutions. During an incident, VictorOps serves as a central hub that has all the tools your devops team needs to resolve the incident.
Like we mentioned earlier, communicating with internal teams should be part of that process. Since most of the other tools you need to resolve an incident are already at your fingertips in VictorOps, we thought we’d add StatusPage.io to that list.
You can create/update incidents on your status page as well as update the status of your components right within the VictorOps interface.
Let’s take a look at how to set it up and how it works.
Getting Set Up
You’ll need to enter your StatusPage.io API Key into VictorOps. You can do that by:
To finish setting up the integration, return to VictorOps and input your API Key. You’ll also need to select which page you want to the integration to apply to. (Note: if you don’t whether your account has multiple pages, it’s likely that you only have one.)
Once you’ve added the StatusPage.io integration, you’ll start to see activity on your status page being piped into your VictorOps timeline.
The metadata included in the message will be specific to the type of action you’ve taken in StatusPage.io. For example, when you update the status of a component, it will tell you which component was updated, what the new status is, and who updated it. When you create or update an incident, it will tell you the name and current state of the incident, what the body or message of the actual update is, and who posted it.
The main benefit of having these messages piped into your VictorOps timeline is it helps keep the entire team on the same page with regard to how the incident is progressing.
When your servers are on fire, quickly getting them fixed is of the upmost importance. So we made it as easy as possible to quickly post an update to your status page so you can do just that.
When your website is having problems, it’s likely you already have a tab open in the VictorOps interface. When you enable the StatusPage.io integration in VictorOps, a StatusPage.io icon will appear in the right sidebar where VictorOps incidents are displayed. Clicking that will open a flyout where you can create/update a StatusPage.io incident as well as update the status of a StatusPage.io component.
We’re really excited to be launching this integration. It’s definitely one of the tightest integrations we’ve done so far and we really think you’re going to enjoy using it.
If you’d like to enable this feature, please let us know.