At Blameless, the world’s leading software engineering teams rely on us during incident management. A key part of our offering is the ability to seamlessly integrate with a customer’s unique tech stack. As such, we value partnerships with companies like Microsoft that enhance our user experience and meet the needs of our customers. We understand how essential it is to integrate with communication tools like Microsoft Teams, because it’s the first place a user goes to start an incident.

Incidents happen, so how do you handle them? We explain incident management, how to prioritize incidents, and the process involved to resolve the incident. ‍

Software metrics give important insight into the performance of your product, but which ones matter most to SRE teams? How do you decide which metrics to track?

Whether you’re building an SRE team or looking for a job as an SRE, understanding the SRE job description is important. How would you define an SRE job?

Whether you’re building an SRE team or looking for a job as an SRE, understanding the SRE job description is important. How would you define an SRE job?

Distributed software systems have many points of failure. Can the process of chaos engineering help identify problems and gauge resiliency?

In episode 3 of From Theory to Practice, Blameless’s Matt Davis and Kurt Andersen were joined by Liz Fong-Jones of Honeycomb.io and Jean Clermont of Flatiron to discuss two words dreaded by every engineer: technical debt. So what is technical debt? Even if you haven’t heard the term, I’m sure you’ve experienced it: parts of your system that are left unfixed or not quite up to par, but no one seems to have the time to work on. ‍

Blameless just released a new integration to ServiceNow’s incident management ticketing solution. If you are a modern DevOps team moving towards SRE practices and you want to speed the time to incident resolution through streamlined, automated workflows, this is worth investigating.