Splunk is all-in on OpenTelemetry, as exemplified by our native support for it in Observability Cloud, Splunk Enterprise and Enterprise Cloud’s usage of the OpenTelemetry Collector with Splunk Connect for OpenTelemetry Kubernetes, our long-term ambition to use OpenTelemetry as the main way that all Splunk Products capture data from customers’ infrastructure and applications for analysis, and our massive level of contribution to the project.

OpenTelemetry is a Cloud Native Computing Foundation (CNCF) initiative that provides open, vendor-neutral standards and tools for instrumenting services and applications. Many organizations use OpenTelemetry’s collection of APIs, SDKs, and tools to collect and export observability data from their environment to their preferred backend. As part of our ongoing commitment to OpenTelemetry, we are proud to have contributed our distributed tracing libraries to the CNCF community.

Ruby on Rails is a popular MVC framework for creating web applications. It is necessary to monitor your Ruby applications for performance issues. In today’s cloud-native and microservices-based architecture, it is difficult for engineering teams to troubleshoot performance issues. Tracing your application can give the much needed context required to troubleshoot performance issues.

“Cloud native” – working in distributed systems using microservices and DevOps – has promised a lot, and indeed delivered a lot. Among the biggest benefits, in a cloud-native distributed architecture it’s easier and more cost-effective to scale parts of an application. When one part fails, it is less likely to impact other services and the services can still communicate with each other.

The OpenTelemetry members at observIQ are excited to add Microsoft IIS metric monitoring support to OpenTelemetry! You can now easily monitor your IIS web servers with the oIQ OpenTelemetry Collector. You can add the IIS metric receiver to any OpenTelemetry collector. This post demonstrates just one configuration for shipping metrics with OpenTelemetry components. This configuration and many other observIQ OpenTelemetry configurations are available in the oIQ Opentelemetry Collector.

Dear Miss O11y, How is modern observability using tracing, such as Honeycomb, different from the previous distributed tracing software I'm familiar with, like Dapper, at my company? I haven't really been able to wrap my head around Dapper. Does "advanced" observability mean that it's even more complicated than Dapper is? Auntie Alphabet.

OpenTelemetry can be used to trace Rust applications for performance issues and bugs. OpenTelemetry is an open-source project under the Cloud Native Computing Foundation (CNCF) that aims to standardize the generation and collection of telemetry data. Telemetry data includes logs, metrics, and traces. Rust is a multi-paradigm, general-purpose programming language designed for performance and safety, especially safe concurrency.

Greetings friends, one and all! Over here on the Field Engineering team, we’re often asked about tracing. Two questions that come up frequently: Do I need to sample my traces? and How do I sample my traces? The folks asking are usually using tracing stores where it’s simply not possible to store all of the traces being generated. Those are great questions and the answers depend on a few different factors.

OpenTelemetry can be used to instrument your Elixir applications to generate telemetry data. The telemetry data can then be visualized using an observability tool to monitor your Elixir application performance. In this tutorial, we will use OpenTelemetry Elixir libraries to instrument an Elixir application and then visualize it using SigNoz. Somewhere during the lifetime of an application, it's inevitable that it will have some performance issues.