From the course: Mastering Observability with OpenTelemetry

Unlock the full course today

Join today to access over 24,700 courses taught by industry experts.

Introduction to the OpenTelemetry Collector

Introduction to the OpenTelemetry Collector - OpenTelemetry Tutorial

From the course: Mastering Observability with OpenTelemetry

Introduction to the OpenTelemetry Collector

- [Instructor] In this chapter, we are going to set up an OpenTelemetry Collector, but why would we do that in the first place? Let's revisit OpenTelemetry's architecture real quick. We see that the Collector provides a receive, process, export pipeline, very similar to what the in-app observability code provides already. So what is this Collector good for in the first place? Why could we not just export from the app to the backend as we did now with Jaeger? In fact, OpenTelemetry didn't invent Collectors. Most observability solutions I know use similar components. Let me show you why. So here's our app again, and the observability code runs as part of the app. So it'll produce traces, metrics, and logs, and it'll try to ship off the data to some backend, likely somewhere in the cloud. Networks have a latency, and naturally it'll take its time until the telemetry data makes it out of the process. So the data starts piling up, waiting to be exported, and suddenly your application…

Contents