Sumo Logic nnounced the general availability of Sumo Logic Reliability Management.
Reliability Management enables developers, SREs, and DevOps teams to manage the reliability of their mission-critical apps by adopting a Service Level Objective (SLOs) methodology.
Reliability Management is a new capability of Sumo Logic Observability that helps organizations adopt a fundamentally better approach to measure and improve the reliability of distributed applications. This approach focuses on the reliability of the application from the end user perspective instead of monitoring and alerting across all of the infrastructure, services and application components involved in the response.
“Sumo Logic Reliability Management shifts the focus on reliability from underlying technology components towards the user experience. It enables connecting business concerns with technology behavior. By facilitating alignment between app owners and developers, Reliability Management essentially serves as the master plan required to manage at the business level versus the signal level,” said Erez Barak, VP of Product Development for Observability, Sumo Logic. “Organizations can now find the optimal cadence to balance innovation velocity with service reliability and turn SLO metrics into actionable insights to achieve their performance promises to customers.”
“Some customers are using SLOs to support the journey to the cloud to understand the risk of their transformation better. Now, with this level of detail from Sumo Logic, organizations can not only see where they are stressing infrastructure - they can see the forest for the trees,” said Torsten Volk, Managing Research Director, EMA Research. “You can stop caring about a Kubernetes node misbehaving if it has no impact on your users. You can look at your system outside in. Teams can now focus on what matters and avoid burnout. This is a much-needed piece to gain true observability.”
Sumo Logic Reliability Management also adopted slogen. slogen is built on the OpenSLO standard and uses automation to minimize the effort needed to measure and set SLOs. Sumo Logic customers get the choice of defining SLOs either in Open Source specification or in Sumo Logic.
“We are not reinventing the standard. We are getting behind the OpenSLO standard and have continued our investment in developing this standard for the community,” continued Barak. “With an open solution for service level management, we’re enabling organizations to future-proof their SLOs.”
Sumo Logic Reliability Management helps organizations to be more proactive in delivering digital services by:
- Empowering leaders to balance innovation with service reliability: Sumo Logic Reliability Management provides real-time reliability and performance metrics to power data-driven decision-making. Leaders also gain proactive alerts on SLOs and error budget consumption.
- Delivering a simple, open, and secure approach to service level management: Built on the OpenSLO standard, Reliability Management enables teams to monitor SLIs based on existing Sumo Logic queries. When combined with Terraform support, SREs can effectively manage service levels as code in a versioned and repeatable manner across any number of product and service teams.
- Making good SRE practices a reality: Enables SRE teams to uniformly adopt concepts such as SLIs, SLOs, SLAs and error budgets, and apply them to the business problem of reliability management. By automating data collection and analysis, teams also get a consistent view of SLOs and reliability across various products or services.
Sumo Logic Observability helps reduce downtime and solves customer-impacting issues faster with full-stack observability for all application data including logs, metrics, events and traces across the entire development lifecycle.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...