馃憢 Hey folks
Don't you hate it when you copy and paste something and lose all of your beautiful, shiny formatting? Especially when you've spent hours getting it right? We do, too.
Well, now this is a thing of the past when it comes to post-mortems. But we didn't stop there. Keep reading to learn about this, and other features we launched in February 馃敟
Oh, and be sure to check us out at SRECon later this month if you want a peek at what we have in the pipeline鈥攎ore details below. We promise it'll be worth your time 馃槃
Export your debriefs to Google docs
This is one we鈥檙e really excited about鈥攅xporting your incident post-mortems directly into Google Docs!
When you export your post-mortem, all key details about your incident will be carried over, including an end-to-end timeline of everything that happened. Now, all of your post-mortems will exist in a single place, so you can track them down in seconds.
Wave goodbye to copy-paste and enjoy beautifully formatted post-mortems you can glean takeaways from at a glance.
Get connected with Webhooks
You asked, and we listened.
Now incident.io users can use webhooks to push data to an app's endpoint. When we first built our API, we got a lot of feedback from customers who wanted to plug our platform into different tools. The API was the first step towards this鈥攚ebhooks take care of the other part.
Through webhooks, you can listen for changes and perform actions such as syncing follow-ups or warning about ongoing incidents during code deploys.
Pulling data from Datadog
Incident management is all about speed and pace. And when there鈥檚 a high-severity incident, the last thing you want to be doing is bouncing around different links trying to find the information you need to diagnose the issue.
That鈥檚 why we鈥檝e just released an integration with Datadog. When incidents are triggered using Pagerduty or Opsgenie, we鈥檒l automatically pull information about any Datadog monitors that triggered that alert. Then when you join that incident channel, you鈥檒l see a host of relevant information, including:
- The name of the offending Datadog monitor, along with a link to explore more at that point in time
- An image of the monitor, so you can see its recent history and determine if it gradually got worse or if it was a sudden spike
- Up to 500 characters of the description of your monitor
- 鈥nd more
We're SSO excited about SAML!
Single Sign-On via SAML is now enabled! Now users can quickly and easily access their incident.io dashboards using their current SAML provider, such as Okta. The time savings here are hard to overstate鈥攏ow admins can control user or group access in bulk to incident.io.
And watch this space because we'll soon support SCIM 馃帀
The importance of transparency
Regardless of the size of your company, practicing transparency across all aspects of your day-to-day can be a game-changer. It鈥檚 something that we wholeheartedly believe in here at incident.io.
But why should you adopt it in the first place?
In this article, we explore why we鈥檝e made transparency a key part of our culture and explain why you may want to do the same.
Non-technical teams should be declaring incidents, too
Incident management is something usually delegated to technical teams, e.g., engineers. And in many ways, that feels like the most rational and reasonable decision. But the reality is that companies should not only empower but encourage non-technical teams to declare incidents.
Check out our article to learn why.
We鈥檙e going to SRECon!
We鈥檝e been busy planning for our first conference of the year: SRECon US. The team will be in Santa Clara, CA, from March 21-23rd.
Come by Booth 400 to say hi!
Looking forward to seeing lots of you there.
