![]() As a Gateway running in a dedicated server, container, or deployment.As an Agent running on the same host as your instrumented application, either as a local service, sidecar, or daemonset.The Collector can be deployed in two ways: In this post we’ll take a look at how it can be installed and configured. So the OpenTelemetry collector is a Go binary that does exactly what its name implies: it collects data and sends it to a back-end. Unified: Single codebase, deployable as an agent or collector with support for traces, metrics and logs. Observable: An exemplar of an observable service.Įxtensible: Customizable without touching the core code. Performant: Highly stable and performant under varying loads and configurations. Usable: Reasonable default configuration, supports popular protocols, runs and collects out of the box. Jaeger, Prometheus, etc.) sending to multiple open-source or commercial back-ends. In addition, it removes the need to run, operate and maintain multiple agents/collectors in order to support open-source telemetry data formats (e.g. The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data. The GitHub readme does an excellent job of describing the collector: The OpenTelemetry Collector is an application written in Go. The OpenTelemetry project is not involved with how the data is stored, displayed, or used beyond the collection and transmission phases. The scope of the OpenTelemetry project encompasses how telemetry data is collected, processed, and transmitted. Engineering Installing and Configuring the OpenTelemetry Collector Overview
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |