ADOT supplies instrumentation, collectors, and exporters for sending application telemetry to AWS monitoring destinations. Follow the data from the application to its destination, including credentials and protocol requirements.
Instrumentation, collectors, and exporters
AWS Distro for OpenTelemetry (ADOT) provides AWS-supported tools for application telemetryMeasurements and events that describe the behavior of a running system., the measurements and events used to understand a running system. InstrumentationCode or configuration that makes an application generate telemetry. creates the data; a collectorA process that receives, processes, and exports telemetry. can process and route it; exportersA component that sends collected telemetry to a destination. send it to monitoring destinations.
A metricA measurement of a running service. is a measurement. A traceA record of the path of one request through a system. follows one request through an application, and a spanA record of one operation within a trace. describes one operation within that trace.
How it works
- Instrument the application with a software development kitA set of software tools and libraries used to add application functionality. (SDK) or supported automatic instrumentation. Deploying a collector alone does not make the application emit traces.
- Configure receiversA collector component that accepts telemetry or retrieves it from an exposed endpoint.. An OTLPA protocol for delivering OpenTelemetry data to a collector or monitoring endpoint. receiver accepts OpenTelemetry Protocol data from instrumented applications. A Prometheus receiver scrapes metrics, meaning it reads measurements from exposed endpoints.
- Add processorsA collector component that changes or groups telemetry before export. to batch data, filter it, change attributes, or sample traces. SamplingSelecting a subset of traces to record. selects a subset of traces to record.
- Connect the receivers, processors, and exporters in
service.pipelines. Enable needed extensions, such as authentication helpers, inservice.extensions. - Export traces to X-Ray or metrics to CloudWatch or Amazon Managed Service for Prometheus (AMP). For Prometheus remote writeSending collected metrics to a remote Prometheus-compatible storage endpoint., which sends collected metrics to a workspace, configure
prometheusremotewrite,sigv4auth, signing serviceaps, the workspace Region, and credentials with remote write permissions. SigV4AWS request signing that authenticates requests using AWS credentials. is AWS request signing that authenticates a request using AWS credentials. - Choose the deployment form for the workload. ECS uses a sidecarAn additional container that runs beside an application container to provide a supporting function., an additional container beside the application, with destination permissions in its task roleThe IAM role that grants an ECS task permission to call AWS services.. EKS can manage the ADOT OperatorA component used to manage OpenTelemetry collection on a Kubernetes cluster., a component that manages OpenTelemetry collection. Collectors can run on EC2 or on-premises hosts. Supported Lambda functions can use AWS-managed ADOT layers that package instrumentation and collection configuration.
| Component | Role | Example |
|---|---|---|
| Instrumentation | Generates application telemetry | SDK code or automatic instrumentation |
| Receiver | Brings telemetry into the collector | OTLP input or Prometheus scrapingReading metrics from an endpoint exposed by an application or infrastructure component. |
| Processor | Changes or groups telemetry before export | Batching, filtering, sampling |
| Exporter | Sends telemetry to a destination | Prometheus remote write |
Supported ADOT SDKs can also export directly without a collector. For direct traces, enable Transaction Search and use https://xray.<region>.amazonaws.com/v1/traces. The documented SDK setup uses AWS credential providers and an application role with AWSXrayWriteOnlyPolicy. A collector remains useful when telemetry needs shared processing or routing.
Exam cues
- If the question says ECS has a collector but no application traces, think instrument the application and check its task role, because the sidecar needs emitted data and destination permissions.
- If the question says one instrumentation setup must serve several monitoring destinations, think ADOT collector exporters, because collection can route telemetry to different services.
- If the question says EKS metrics are scraped but AMP ingestion fails, think remote write signing and permissions, because collecting a metric does not authorize exporting it.
- If the question says direct SDK export to the X-Ray OTLP endpoint, think Transaction Search, because the endpoint requires it even without a collector.
Remember
- Collector sequence: receivers, processors, exporters.
- AMP signing service:
aps; use the workspace Region and remote write permissions. - AWS OTLP endpoints accept HTTP, not gRPC, a different remote-call protocol.
- The documented collectorless Java path requires ADOT Java Agent 2.11.2 or later. It uses
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT,OTEL_TRACES_EXPORTER=otlp, andOTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf.
Trap: The collector and application instrumentation solve different parts of the flow. A healthy collector does not prove the application is producing traces.
Trap: A Prometheus receiver reads metrics;
prometheusremotewritesends them. Replacing one with the other reverses the direction of the data flow.
Instrumentation emits telemetry for the collector to receive.
A configured trace exporter sends traces to X-Ray.
A configured metric exporter sends metrics to CloudWatch.
The Prometheus remote write exporter sends metrics to the workspace.
The instrumented application exports traces directly to the X-Ray OTLP endpoint with Transaction Search enabled and destination permissions.
Da documentação da AWS (30)
- ADOT is an AWS-supported distribution of OpenTelemetry SDKs, auto-instrumentation agents, and collectors.
- Instrumentation makes an application emit telemetry through code or supported automatic instrumentation.
- Telemetry includes metrics, logs, and traces describing application behavior.
- A metric is a measurement of a running service.
- A trace records a request path and contains spans representing individual operations.
- An OpenTelemetry Collector receives, processes, and exports telemetry from applications and other sources.
- A collector can batch, filter, add or remove attributes, and sample telemetry before export.
- An OTLP receiver accepts telemetry from applications using OpenTelemetry SDKs.
- A Prometheus receiver scrapes metrics from Prometheus-compatible endpoints.
- Collector configuration wires receivers, processors, and exporters under service.pipelines and activates extensions under service.extensions.
- ADOT can send telemetry to AWS monitoring destinations including X-Ray, CloudWatch, and Amazon Managed Service for Prometheus.
- ADOT can send scraped metrics to an Amazon Managed Service for Prometheus workspace through prometheusremotewrite.
- The AMP exporter uses sigv4auth with signing service aps and the workspace Region.
- The collector must obtain AWS credentials with remote write permissions for Amazon Managed Service for Prometheus.
- EKS can install and manage the ADOT Operator to support metric and trace collection.
- ECS can run an ADOT sidecar container to collect application traces and route them to X-Ray.
- An ECS application must be configured to generate traces before its ADOT collector can send them to X-Ray.
- ECS ADOT integration requires a task IAM role in the task definition with permissions for the telemetry destinations.
- An OpenTelemetry Collector can run on EC2 or an on-premises host with destination credentials configured.
- AWS-managed ADOT Lambda layers package OpenTelemetry with Lambda and X-Ray configuration and can automatically instrument supported functions.
- Supported ADOT SDKs can export telemetry directly to AWS OTLP endpoints without a collector.
- Sending spans to the X-Ray OTLP endpoint requires Transaction Search to be enabled.
- The X-Ray OTLP traces endpoint is https://xray.<region>.amazonaws.com/v1/traces.
- AWS OTLP endpoints support HTTP, not gRPC.
- The documented ADOT SDK trace export setup grants AWSXrayWriteOnlyPolicy to the application role.
- ADOT SDKs discover export credentials through AWS SDK credential providers.
- The documented collectorless Java export configuration requires ADOT Java Agent 2.11.2 or later.
- The documented ADOT Java setup uses OTEL_EXPORTER_OTLP_TRACES_ENDPOINT for the endpoint, OTEL_TRACES_EXPORTER=otlp, and OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf.
- Sampling selects a subset of traces to record.
- A Prometheus receiver collects metrics into a collector, while a Prometheus remote write exporter sends collected metrics to the destination workspace.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 10 flashcards em lista
What does the AWS Distro for OpenTelemetry collector do, and where can telemetry go?
It receives, processes, and exports telemetry. Destinations include X-Ray for traces and CloudWatch or Amazon Managed Service for Prometheus for metrics.
Can an application use ADOT to send traces to X-Ray without a collector?
Yes. Use a supported ADOT SDK and the X-Ray OTLP traces endpoint. Enable Transaction Search and configure the documented export permissions, credentials, and HTTP protocol.
Does deploying an ADOT collector automatically instrument an ECS application?
No. The application must generate traces through instrumentation. The sidecar receives and forwards that telemetry.
An ECS application has a running ADOT sidecar but no application traces in X-Ray. What should the team check first?
Check that the application is instrumented and emits traces, then check the task role permissions for the destination. A running sidecar alone does not create application traces.
An Amazon ECS application emits traces, but its ADOT sidecar cannot send them to X-Ray. Which permissions should the team check?
Check the ECS task IAM role for permissions to send telemetry to X-Ray.
A supported ADOT SDK sends traces directly to the X-Ray OTLP endpoint, but Transaction Search is disabled. What prerequisite is missing?
Enable Transaction Search before sending spans to the X-Ray OTLP endpoint. Collectorless export still requires this setting.
What is the ADOT collector processing sequence?
Receiver, processors, exporter. Receivers accept or scrape telemetry; processors can batch, filter, or sample it; exporters send it to monitoring destinations.
An ADOT collector receives application traces, but its X-Ray exporter is not referenced in the trace pipeline. What should the team change?
Connect the receiver, processors, and exporter in the collector service.pipelines configuration.
A Lambda team wants supported automatic instrumentation for X-Ray traces using ADOT. What can it configure?
Use an AWS-managed ADOT Lambda layer that packages OpenTelemetry with Lambda and X-Ray configuration.
Which ADOT deployment forms fit EKS, ECS, and Lambda?
EKS can manage the ADOT Operator. ECS can run a collector sidecar. Lambda can use AWS-managed ADOT layers for supported function instrumentation.