AWS Distro for OpenTelemetry
AWS Distro for OpenTelemetry Collector Configuration
AWS Distro for OpenTelemetry Collector Configuration
Collector Configuration Introduction
After the ADOT Operator is running in your cluster, you can deploy the ADOT Collector as a custom resource. In these instructions, we will deploy a Collector in Deployment mode to perform the following:
- Scrape metrics and traces inside your EKS cluster.
- Ingest the metrics to Amazon Managed Prometheus
- Ingest metrics for CloudWatch
- Ingest traces for X-Ray.
Traces are received in OpenTelemetry Protocol (OTLP) format. Metrics are received in Prometheus format. Other deployment modes of the Collector, such as the Daemonset or Statefulset mode are called for in more advance use cases. We explore one of these advanced use cases here. For more information about Collector configuration, as well as OTLP and Prometheus receiver configurations, Amazon Managed Prometheus, CloudWatch, and X-Ray exporter configurations, and Sigv4 authentication extension configurations, refer to the documentation below:
- Collector CRD configuration
- OTLP Receiver configuration
- Prometheus Receiver configuration
- Prometheus Remote Write Exporter configuration
- AWS CloudWatch EMF Exporter configuration
- AWS X-Ray Exporter configuration
- Sigv4 Authenticator Extension configuration
Below, we have our three Collector configurations, one for Amazon Managed Prometheus, CloudWatch, and X-Ray each. Note that it is possible to combine Collector configurations together, i.e. you can have a Collector set up with more than one receiver, processor, or exporter, and multiple pipelines will be built based on that.