For the past four years, Catchpoint and various partners have been running a yearly SRE Survey. This year, Blameless is excited to partner with Catchpoint for the fifth annual survey. We want to hear from you if you are in a DevOps or SRE role or even if you work on reliability with some other title or role. There are tremendous, valuable learnings when we listen closely to practitioners.

One of the most critical aspects of monitoring your digital assets is getting a timely alert when something goes wrong. Even when you finish building a monitoring stack and expose metrics on a beautifully designed dashboard if you cannot notice abnormal behaviors and fail to take pre-emptive or follow-up actions swiftly, this means your monitoring system does not serve the purpose.

In a world of digital everything, teams face increasing complexity. Ever-growing dependencies across systems and processes put customer and employee experience, not to mention revenue, at risk. There is simply too much data to sift through and correlate for humans to understand what is important and know when something is going wrong.

Customer-facing teams have their hands full doing whatever they can to address customer issues quickly. At PagerDuty, our goal is to ease the burden of these teams by giving them the tools and access they need to deliver excellent customer experiences. Over the last year, we have deepened our integration with Salesforce Service Cloud, allowing users to work directly within the platform, reducing the need to context switch.

We know our customers rely on PagerDuty as the backbone of critical real-time operations, so we want to make sure each and every enhancement helps streamline incident response. How can we help our customers spend less time firefighting and more time innovating? One of PagerDuty’s values is Champion the Customer – and we take this very seriously. When building and improving features, we aim to keep a pulse on what’s going on with our customers: what’s keeping them up at night?

Insight Partners is a leader in working with scale-up companies that have existing product/market fit and can use our help establishing best practices for their businesses. But my specific focus is in developer-driven companies. I look for the best technical teams that are building products that developers love and adore.

Kelverion Runbook Studio V5.0 makes it even easier for organizations to automate IT service desk requests and reduce IT burden. In its fifth iteration, The Runbook Studio has undergone a significant design overhaul. The Studio’s technical capabilities have always been exceptional and now it has a user interface to match. On top of that, this version takes Kelverion’s low code/no-code design environment to the next level.

Curious about the incident priority matrix? We discuss how to determine the impact and urgency of an incident, and how to create a matrix that helps prioritize incidents.

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. Declaring the first incident when you start a new job can be intimidating, but it really shouldn’t be.