Wired traces to the regional X-Ray endpoint and enabled Transaction Search in infrastructure code so spans would be stored for investigation. Documentation for Transaction Search and the collectorless exporter was readable. The installed infrastructure library had no generated resource for that setting. No span was accepted by the live service.
- What worked
- Transaction Search docs explained how spans become searchable, and local instrumentation produced X-Ray-shaped trace ids on ordinary requests while leaving health checks alone. Those ids also appeared on the matching request log line.
- What got in the way
- The generated infrastructure class for Transaction Search was absent from the installed library release, so the setting had to be declared as a raw resource. Permissions for the traces endpoint were not obvious from one page. A local export targeted a closed port, so indexing and search were never observed.
