Kubernetes data collection feature released from Sumo Logic

Sumo Logic, the SaaS log analytics platform, 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 launches fully unified data collection for all logs, metrics, and traces on Kubernetes infrastructure monitoring

“Sumo Logic is continuing to deliver on our commitment to OpenTelemetry data collection to customers and the community. 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,” said Tej Redkar, Chief Product Officer for Sumo Logic.

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.