incident.io Reviews and Details

Is incident.io good?

Social recommendations and mentions

• Send incident.io Status to New Relic with Synthetics

  Here's a quick way to monitor a status page hosted by incident.io with New Relic. Specifically, I'll be using Synthetic monitoring to achieve this with a Scripted API test. - Source: dev.to / about 1 year ago

• Incident Write-ups

  There are SaaS products out there that can help with data collection like incident.io or firehydrant.io to more quickly construct a timeline. Source: over 2 years ago

• Seeking Opinions on Atlassian Statuspage Alternatives

  My new favourite is https://incident.io. Great UI, great product, especially if you also need an incident management tool. Source: over 2 years ago

• What was the biggest or most interesting incident you worked on?

  We did a pretty detailed write-up about a significant incident we had a few months back at incident.io: https://incident.io/blog/intermittent-downtime. Source: over 2 years ago

• rootly Vs firehydrant, any experience?

  Co-founder of incident.io here, so I'll avoid throwing my thoughts around for obvious reasons. Source: over 2 years ago

• Postmortems, tracking and keeping them

  I work at a company that offers a platform for this called https://incident.io/. Source: over 2 years ago

• SRE: What tool do you use for Incident Response Runbook/Playbook

  These days there are many tools for SRE Incident Response like incident.io, Blameless, root.ly, FireHydrant, etc. PagerDuty also has built-in incident response capabilities. Source: over 2 years ago

• What are the best practices around developing RBAC

  We built RBAC into our product (https://incident.io/) about a year ago, and made our proposal doc public: https://www.notion.so/incidentio/Proposal-Product-RBAC-265201563d884ec5aeecbb246c02ddc6. Source: almost 3 years ago

• Build your own PagerDuty with Go in just 30 minutes

  In this tutorial, we're going to walk through together how to build our very own Incident Management Tool like Incident.io or PagerDuty. We can then have our own on call schedule that can be rotated between many users, and have incidents come and be assigned according to the schedule! - Source: dev.to / about 3 years ago

• Free on-call pay calculator for those who use PagerDuty

  Today we're (https://incident.io) releasing our on-call pay calculator for free, removing the need for an incident.io account entirely. Source: about 3 years ago

• Events tracking in Firehydrant from Slack

  Hey 👋 I work at incident.io and we're literally starting work on a feature to allow for tracking of arbitrary events/timestamps in incidents. Feel free to shoot me an email if you want to chat or hear more about what we're thinking: chris@incident.io. Source: about 3 years ago

• Events tracking in Firehydrant from Slack

  Heya, I think incident.io incorporates this. There is also a YC backed alternative, that copied a lot of it. But I think that incident.io is better.. I just found it a bit pricy. So we just write postmortems by hand :) And log our stuff afterwards. But if there would be less resistance I would totally incorporate it. Source: about 3 years ago

• monitoring and alerting

  Now, I could use something like prometheus or Splunk or sentry.io or statuspage or incident.io (these are all used at the company), but this seems 1) overkill seeing as the alerts prebuilt into Meraki already handle specific events that we're concerned with and 2) far too involved for something this basic of an ask. Source: about 3 years ago

• Tracing Gorm queries with OpenCensus & Google Cloud Tracing

  At incident.io we use gorm.io as the ORM library for our Postgres database, it's a really powerful tool and one I'm very glad for after years of working with hand-rolled SQL in Go & Postgres apps. You may have seen from our other blog posts that we're heavily invested in tracing, specifically with Google Cloud Tracing via OpenCensus libraries. A huge amount of our application's time is spent talking to Postgres... - Source: dev.to / about 3 years ago

• Incident Response Tooling Best Practices

  When I was at Monzo (a fintech here in the UK) I wrote some basic tooling to help augment the way we were communicating and learning from incidents and it worked really well. Everyone knew the process, folks were kept in the loop, and what used to be a bit chaotic was turned into something a lot calmer and more structured. It was sufficiently successful that a few of us turned it into a company with incident.io.... Source: about 3 years ago

• How to record incidents and post mortems?

  Disclaimer: I’m an engineer here, but https://incident.io is a great tool for exactly this, it was inspired by the tooling and processes we built back when a bunch of us were working in fintech and had to take incidents very seriously. It works inside slack, providing automation to create incident channels and record what goes on inside them, pulling data automatically into the incident timeline, and letting you... Source: over 3 years ago

• We've built an on-call pay calculator for those who use PagerDuty

  Right now it's available for https://incident.io/ customers only, but if we see demand we may consider exposing this for everyone too (doing so would require more work, so we'd like to validate people want it first). Source: over 3 years ago

• Declare early, declare often: why you shouldn’t hesitate to raise an incident

  My first incident.io-incident happened in my second week here, when I screwed up the process for requesting extra Slack permissions, which made it impossible to install our app for a few minutes. This was a bit embarrassing, but also simple to resolve for someone more familiar with the process, and declaring an incident meant we got there in just a few minutes. - Source: dev.to / over 3 years ago

• Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io

  At incident.io, we ship fast. We're talking multiple times a day, every day (yes, including Fridays). Once I merge a pull request (PR), my changes rocket their way into production without me lifting a finger. 💅 It's when we tackle larger projects that this becomes a bit more complicated. - Source: dev.to / over 3 years ago

• How to empower your team to own incident response

  Moving to incident.io as the 7th engineer, from a scaleup of around 70 engineers, has given me a new perspective on what it means to own your code. Switching from somewhere with a centralised platform team who hold the pager and coordinate response, to being part of the on-call rotation has been really eye-opening. - Source: dev.to / over 3 years ago

• How much should you get paid for being on call?

  As some background, our company (https://incident.io/) offers Slack-based incident response tooling, and have a load of customers who are keen to get better insight and tooling into managing on-call. Source: over 3 years ago