Sumo Logic announced the availability of its HELM Chart V4 feature to fully unify data collection as part of its continued commitment to OpenTelemetry (OTel).
Organizations can now package, configure and deploy applications and services on Kubernetes clusters with OpenTelemetry as a default to simplify the collection of metrics, events, logs and traces.
Sumo Logic HELM Chart V4 removes dependencies on disparate third-party solutions like Fluentbit, Fluentd and Prometheus to reduce data collection complexity and cost. By fully unifying collection for all logs, metrics and traces, organizations can save the cost of managing multiple agents. Organizations can also optimize their deployment lifecycle while minimizing required updates and potential security risks. OTel collection also provides significant performance with less CPU consumption for additional cost efficiencies.
“Sumo Logic is continuing to deliver on our commitment to OpenTelemetry data collection to customers and the community,” said Tej Redkar, Chief Product Officer for Sumo Logic. “Sumo Logic HELM Chart V4 evolves the collection experience for Kubernetes by using OpenTelemetry as its standard collector, and will help our customers get the insights they need to take action to uncover and resolve performance issues quickly, so DevOps teams can spend less time troubleshooting issues, and do what they do best - deploy code.”
Sumo Logic HELM Chart V4 fully unifies the OpenTelemetry pipeline to provide real-time operations insights for digital business through:
- Unified collection - unified Kubernetes monitoring is now available through a single agent for all signals - logs, metrics, traces and events.
- Auto-instrumentation - correlated telemetry and auto-instrumentation provide a simplified collection process to reduce the chaos of managing disparate third-party collection agents to process monitoring signals.
- Pre-canned configurations - running a single agent for all data types allows for a smaller, more efficient data collection footprint, giving customers quicker application infrastructure setup and a smoother experience to help drive adoption with developers and DevOps teams.
The Latest
For decades, traditional observability tools have forced IT professionals to sift through endless dashboards, turning a flood of alerts into actionable insight and driving widespread burnout. While enterprises adopted AI to eliminate this friction, most still deploy it reactively rather than proactively ... As systems become more complex and IT moves to the center of business strategy, a reactive posture is unsustainable ...
Ask an operations team what they monitor and you will hear a familiar list: latency, errors, throughput, uptime. Those signals still matter for AI, but they no longer answer the most important question. As Krishna Sai, CTO of SolarWinds, puts it: "Traditional observability tells you a system is running. AI observability tells you whether it's still reasoning soundly. Those are completely different questions" ...
AI observability serves several roles across an organization. AI engineers use it to build, evaluate, and improve AI systems. SREs use it to operate those systems reliably and efficiently in production, including managing their cost. Leaders need it to connect AI behavior and operational performance to business outcomes. The common need is a clear understanding of whether AI systems are delivering the intended result ...
Part 4 outlines the challenges enterprise face when adopting AI observability. The main challenge is that AI complexity compounds at every stage of maturity. LLM-based applications introduce new behavior, dependencies, and quality considerations, while Agentic AI adds further failure modes as systems make decisions and take actions ...
Part 3 reports on the current state of AI observability. Most experts agree: enterprises are moving faster with AI than they are with the operational discipline needed to run it safely ...
When discussing AI Observability, one of the first questions that arises: Is this just an extension of traditional observability or is this a whole new type of tool? Part 2 compares traditional observability with AI observability ...
In this extensive 14-part series that will post over the next three weeks, experts across observability and AI will provide insight and opinions on the need for AI Observability, the challenges, the benefits, the current state, and predictions for the future ...
Amid rising complexity, organizations are moving quickly toward agent-driven operations: AgenticOps, according to The Impact of Agentic AI on Network Operations, a new report from Cisco ...
AI, automation, and enterprise software give organizations an extraordinary amount of leverage. Work that once required hours can happen in minutes. Information buried across systems can be analyzed almost instantly. Complex workflows can be coordinated across teams with far less manual intervention. That leverage creates a temptation to start with the technology ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...