We are thrilled to announce that Grafana Incident is now generally available to all Grafana Cloud users, including our generous free tier. (You can sign up for a free Grafana Cloud account now.)

If you’re familiar with PagerDuty, you probably associate it with alerts about technical services behaving in ways they shouldn’t. Maybe you yourself have been notified at some point that a service wasn’t available, was responding slowly, or was returning incorrect information. That’s the common use of a service in the PagerDuty platform.

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.

Meetings are a necessary evil in any workplace. They can be long, tedious, and often unproductive. But post-mortem (PM) meetings are different. They are one of the most valuable meetings a service-oriented organization can have. Post-mortem meetings are an essential part of any project manager's toolkit. They provide an opportunity to reflect on what went well and what could be improved upon in future projects.

Over the last couple of months and service releases, we made continuous efforts to enhance Derdacks capabilities to collect, aggregate and alert shopfloor incidents for our Industry customers that primarily use OPC for alerting. In the accompanying projects, we made big improvements to our OPC Integration even added additional features. The OPC integration received a complete overhaul of the configuration and data management systems and can now handle OPC UA Alerts&Conditions.

Not many companies will tell you why you shouldn’t use their product, but any product that tries to be everything to everyone is doomed to failure. When you build without a specific user in mind, your target becomes the intersection of many viewpoints, and what you build is the lowest common denominator. What usually follows is software that can technically do everything, but feels unfocused, complex, and unpleasant to use. Something everyone is equally unhappy with.

Today, we’re announcing major new updates to Honeycomb’s PagerDuty integration. These updates put more of the information you need into PagerDuty notifications and allow for greater configurability. These enhancements are available to all users who leverage Honeycomb Triggers and Burn Alerts to send notifications via PagerDuty.

What’s just as important as resolving an impacted service? Providing detailed yet digestible updates to your communities and stakeholders. A recent update to StatusCast, involves the addition of three new status types that can be assigned to your components. Detailed communications is an essential component of incident response and management, and additional status types provide your users with a more granular view of incident activity.

How are you tracking the long-term operation and health indicators for your micro and macro services? Service Level Indicators (SLIs) and Service Level Objectives (SLOs) are prized (but sometimes “aspirational”) metrics for DevOps teams and ITOps analysts. Today we’ll see how we can leverage SignalFlow to put some SLOs Error Budget tracking together (or easily spin up same with Terraform)!