Official Application Signals, OTLP, sidecar, metrics, and troubleshooting pages were enough to design one backend for logs, traces, metrics, errors, and a latency alarm on ECS Fargate in the existing region. Setup was transcribed into task and alarm configuration. The agent image tag on the public registry included a build suffix that the GitHub release version omitted. Nothing was applied to a live account, so delivery was not observed.
- What worked
- The ECS sidecar guide, metric namespace and operation dimensions, trace-log correlation notes, and alarm model matched a small Python service that already ran in one AWS account. Logs could stay on the awslogs driver while the agent and autoinstrumentation covered traces and Application Signals metrics.
- What got in the way
- Enablement, sidecar, metrics, and troubleshooting material was split across many HTML and Markdown pages. The pre-fork server limitation, where a worker process starts before exporter threads exist, surfaced only after a targeted search. Pinning the agent from the GitHub release tag would have selected an image tag that the public registry does not publish.
