OpenTelemetry Profiling Explained: How It Works and Why It Matters

If you're looking for a content explaining what is open telemetry profiling, then this episode is for you. [music] [music] Welcome back to the is it observable YouTube channel. Today's episode will be part of the open telemetry playlist where I covered already lots of various content such as open telemetry metrics, instrumentation logs, uh usage of the collector to instrument to measure your Kubernetes cluster. There's [snorts] a lot of them. So if you never watch any openmetry content on this channel, check out the following playlist. I usually try to create episode presenting one of the core signal or core feature of open telemetry and in fact it to be honest it's been a while that I did not cover any open 3D content but I'm today I'm very excited because we were going to focus on the latest signal of open telemetry that is often overlooked but incredibly powerful and it's profiling. In this episode, I will try to share all the details on how to produce profiling, uh the state of profiling, how to process profiling, uh and share details on the current work from our community. If you enjoy today's content, don't forget to like and subscribe to the channel. Let's have a look at what we're going to talk about in this episode. We'll start with explaining when we should use one of the signals of open. profiling traces, metrics and logs. Then we look at the current state of the open telemetry profile. Explain what is the profiling in general. Look at the open telemetry uh profiling schema because it's going to be important especially when you will We'll explain how to produce and collect profiling data using our collector. We'll look at the current processors and connectors available in the connector. And last because it's going to be useful look at the open telemetry transform language support for profiling. [music] Open telemetry have already three signals metrics traces and logs. So no news for you I'm pretty sure about that. Some of you may ask what are the purposes of each signals and when should we use it? The simple answer is well you need all those signals to properly diagnose a given situation. Well that is in fact obvious because it's the main purpose of observability. But each signals are answering a specific questions that we may have around our architecture.