Skip to content

AWS Distro for Open Telemetry (ADOT) - FAQ

  1. Can I use the ADOT collector to ingest metrics into AMP? Yes, this functionality was introduced with the GA launch for metrics support in May 2022 and you can use the ADOT collector from EC2, via our EKS add-on, via our ECS side-car integration, and/or via our Lambda layers.
  2. Can I use the ADOT collector to collect logs and ingest them into Amazon CloudWatch or Amazon OpenSearch? Not yet but we’re working on stabilizing logs upstream in OpenTelemetry and when the time comes, potentially later in 2023 or early 2024 we will support logs in ADOT, see also the public roadmap entry
  3. Where can I find resource usage and performance details on the ADOT collector? We have a Performance Report online that we keep up to date as we release collectors.
  4. Is it possible to use ADOT with Apache Kafka? Yes, support to Kafka exporter and receiver was added in the ADOT collector v0.28.0. For more details, please check the ADOT collector documentation.
  5. How can I configure the ADOT collector? The ADOT collector is configured using YAML configuration files that are stored locally. Besides that, it is possible to use configuration stored in other locations, like S3 buckets. All the supported mechanisms to configure the ADOT collector are described in detail in the ADOT collector documentation.
  6. Can I do advanced sampling in the ADOT collector? We’re working on it, please subscribe to the public roadmap entry to keep up to date.
  7. Any tips how to scale the ADOT collector? Yes! See the upstream OpenTelemetry docs on Scaling the Collector.
  8. I have a fleet of ADOT collectors, how can I manage them? This is an area of active development and we expect that it will mature in 2023, see the upstream OpenTelemetry docs on Management for more details, specifically on the Open Agent Management Protocol (OpAMP).
  9. How do you monitor the health and performance of the ADOT collector?
    1. Monitoring the collector - default metrics exposed on port 8080 that can be scraped by the Prometheus receiver
    2. Using the Node Exporter, running node exporter would also provide several performance and health metrics about the node, pod, and operating system the collector is running in.
    3. Kube-state-metrics (KSM), KSM can also produce interesting events about the collector.
    4. Prometheus up metric
    5. A simple Grafana dashboard to get started:
  10. Product FAQ -