Operations | Monitoring | ITSM | DevOps | Cloud

Whether you’re a seasoned company with 10+ years of operations, or a startup that’s just getting off the ground, making sure you have a good culture of engineering is really important. Not only will this have a significant impact on the folks on your team, it’ll make a big difference with hiring. When everyone knows that your company is the place to be when it comes to culture, attracting really good talent becomes that much easier.

Q1 2024 is officially behind us. So we figured that it was a great time for a bit of reflection on the exciting start to the year. In this episode, we sit down with our founders, Stephen, Chris, and Pete, to get a bit of perspective on how the last three months played out. We chat about On-call, our AI launch, and the hundreds of other features, bug fixes, and bits of polish and delight that we've shipped over the last 12 weeks.

In this video, watch Co-Founder and CPO, Chris Evans, walk through the setup and usage of incident.io On-call.

In this video, we cover the key differences between SLA, SLO, and SLI defining each term and giving real world examples of how they differ. This video was brought to you by PagerTree. On-Call. Simplified. Transcript: SLA vs SLO vs SLI Whats the difference? In this video, we will define these terms, compare them to one another and give real-world examples of how they work.

Service Level Agreements, or SLAs, are essentially a promise or guarantee from the service provider to the customer. They outline the expected level of service, detailing the products or services to be delivered as well as the consequences for missing these service levels. SLAs are typically drafted by legal departments with insights from product managers and are designed to be customer-facing. It sets the stage for accountability and sets clear expectations right from the start.