Splunk launches inventory tool to simplify OpenTelemetry monitoring

“One of the challenges that people sometimes have with OpenTelemetry is their ability to configure it, validate where it has been deployed, if it’s running properly, if it’s configured properly, and critically, if there is anywhere they haven’t yet deployed it where they need to go actually get that done,” says Morgan McLean, OpenTelemetry co-founder and senior director of product management for Splunk Observability Cloud.

Splunk’s new Service Inventory addresses the challenges of large-scale observability by reducing manual configuration, simplifying instrumentation, and giving customers more transparency and control of their observability processes. The new capabilities in Service Inventory:

• Provide end-to-end visibility, which automatically detects all third-party applications, like databases and message queues.
• Offer configuration guides, which provide step-by-step recommendations for OpenTelemetry setup.
• Identify and resolve visibility gaps, which highlights missing instrumentation, letting enterprises proactively address blind spots across their infrastructure.

With this release, Splunk also enhances its Kubernetes monitoring and troubleshooting capabilities to help teams more quickly detect and resolve issues within Kubernetes clusters. Splunk is also rolling out OpenTelemetry Python 2.0 and Node.js 3.0, which the company says will deliver greater flexibility and improved performance for cloud-native applications.