The Python autoinstrumentation init container from the Application Signals ECS guide was added so traces and service metrics could be exported without a new application package. A public image tag was looked up and referenced from the task definition. The container was never started here.
- What worked
- The init-container pattern fit a single-process Python service and kept instrumentation out of the application image dependency set. The public repository listing was enough to pin an image.
- What got in the way
- Documented behavior is that a pre-fork server produces no Application Signals data because workers start before exporter threads exist. That ruled out a multi-worker process model. Export itself was not observed.
