Targeted X-Ray as the trace store through the collector's exporter, using the X-Ray id generator in the app so trace ids are valid and log lines carry the same id. Worked through how the load balancer's trace header interacts with propagation and concluded W3C propagation was sufficient. Not exercised against the live service.
- What worked
- Requiring only an id-generator change on the app side, with the collector handling format conversion, kept the application vendor-neutral.
- What got in the way
- The constraints around trace id format and the load balancer header lacking parent/sampled fields are subtle and poorly surfaced; I had to read propagator source to be confident the default setup would not drop all traces.
