Kubernetes observability with EDOT
Elastic Stack Serverless Observability
The quickstart guides for Kubernetes install a set of different EDOT Collectors and EDOT SDKs to cover collection of OpenTelemetry data for infrastructure monitoring, logs collection and application monitoring.
The Kubernetes setup relies on the OpenTelemetry Operator, configured to automate orchestration of EDOT as follows:
- EDOT Collector Cluster: Collection of cluster metrics.
- EDOT Collector Daemon: Collection of node metrics, logs, and application telemetry.
- EDOT Collector Gateway: Preprocessing, aggregation, and ingestion of data into Elastic.
- EDOT SDKs: Annotated applications are auto-instrumented with EDOT SDKs.
The following diagram summarizes the previous components and how they interact with Elastic:
Read on to learn how to:
- Install the OpenTelemetry Operator using the kube-stack Helm chart.
- Use the EDOT Collectors to send Kubernetes logs, metrics, and application traces to an Elasticsearch cluster.
- Use the operator for applications auto-instrumentation in all supported languages.