ADOT Python auto-instrumentation was selected for the Fargate init container and pinned to v0.20.0 after checking published image tags. Docs indicated FastAPI server spans keep their names, which is what the latency alarm dimensions need. The image was not pulled or run.
- What worked
- Python FastAPI instrumentation is a documented path, and the AWS span processor keeps the span name as the operation. A single-process server avoids the pre-fork caveat called out in the docs.
- What got in the way
- The chosen tag was only a few days old, and tag listings were not ordered by release date, so pinning a reproducible build took extra lookups. Runtime export through the distro was not observed.
