My role as an Observability Specialist at Splunk provides me with the opportunity to work with customers of all sizes as they implement OpenTelemetry in their organizations. 

If you read my earlier article, 3 Things I Love About OpenTelemetry, you'll know that I'm a huge fan of OpenTelemetry.  But like any technology, there's always room for improvement. 

In this article, I'll share three areas where I think OpenTelemetry could be improved to make it even better. 

In this blog post, I will write about parsing and processing messages to extract information in SOCK. We will explore how to use operators to do so.

In 2022, I made the decision to focus my career on OpenTelemetry.  I was excited by the technology and, after working with proprietary APM agent technology for nearly a decade, I believed that it was the future of instrumentation. 

This ultimately led me to join Splunk in 2023 as an Observability Specialist.  Splunk Observability Cloud is OpenTelemetry-native, so this role allowed me to work extensively with OpenTelemetry as customers of all sizes implemented it in their organizations. 

So how am I feeling about OpenTelemetry in 2024?  Well, I’m even more excited about it than before!  In this article, I’ll share the top three things that I love about OpenTelemetry.   

In this article, we will explore what can be expected from a default configuration for SOCK, and how to enable some extra features.

This article explores more advanced ways of combining multiline log entries into one using OpenTelemetry, by using routing, parser, and recombine operator.

This article explores multiple ways of combining multiline log entries into one using OpenTelemetry, ensuring that complex information is presented in a structured and readable manner.

Got questions? You’re in luck, cause we’ve got answers! Ask the experts at our upcoming Community Office Hours, where technical Splunk experts answer your questions and provide how-to guidance on a different topic every month. Join the 190+ participants who have already benefited from these sessions and register now to secure your spot! 

This article is a code-based discussion of passing OpenTelemetry trace context across STOMP protocol pub/sub with a brokered websocket. This example uses Spring Boot for most components and leverages OpenTelemetry's APIs for manual instrumentation.

What happens if the OpenTelemetry collector cannot send data? Will it drop, queue in memory or on disk? Let's find out which settings are available and how they work!

The Splunk Distribution of OpenTelemetry Ruby has recently hit version 1.0. The distribution provides a Ruby gem for reporting distributed traces to Splunk APM using the Ruby OpenTelemetry SDK.

In this blog post, we will show you how to set up your Heroku app to use our buildpack. We will show off a sample app that is able to use the collector to report metrics, traces and profiling information to the Observability Cloud.

We foresee that next year will be just as amazing as 2022 has been for learning, sharing, and giving!

We are often asked how to copy http request/response headers into OpenTelemetry span attributes. This short tutorial shows you how to do it with the OpenTelemetry Java Instrumentation.

When I had to document how to get data in from Rust applications, I faced an unusually tough challenge. How could I create a snippet for a language I was utterly unfamiliar with and for which we lack a Splunk distribution? The examples in the official OpenTelemetry repository didn't work out of the box. The answer proved simpler than I expected.

A customer was looking for some guidance around adding custom attributes to spans in their Java monolith. To assist, I put together this example repo that shows five subtly different ways of adding manual instrumentation in Java. Maybe you can find it useful, too?

In this blog post, we will explore the best way to check your connection to the HEC endpoint of your Splunk Cloud or Splunk on-premises deployment.

Using a simple curl command, we are sending metrics to signalfx-forwarder endpoint. Instead of sending it to the backend, we are just logging it as debug output.

OpenTelemetry is often associated with modern microservices and cloud-native applications. What happens if we apply OpenTelemetry and modern observability techniques to something completely different? WordPress is the world's most popular weblog software. And it's also an almost 20 years old monolith. What happens if we use OpenTelemetry auto tracing and the Splunk Observability cloud?

In this example, we are going to use our former blog post, ingesting logs from a file and sending them to Splunk Enterprise. We are going to apply a twist to this example by creating three pipelines that read from three different files. Data coming from those three files will be associated with different source types, depending on their source.

This blog post shows how you can use the OpenTelemetry Collector, a Discord bot library, and create a cool solution to follow Discord activity or post alerts.

This blog post will walk you through using the Splunk HEC raw endpoint to send data to the OpenTelemetry collector.

This blog post will walk you through using OpenTelemetry processors to route log data to different indexes depending on its content.

This blog post will walk you through sending metrics data with the OpenTelemetry Collector to a Splunk Enterprise deployment.

Are you looking to try your hand at open source? Curious about OpenTelemetry? This article is for you!

Curious about OpenTelemetry but more interested in logs than APM tracing or metrics? Look no further! This blog post will walk you through your first OpenTelemetry Logging pipeline...