Add Support for AWS X-Ray Tracing Propagator

[scottmace]

Adds support for the OpenTelemetry AWS X-Ray tracing propagator.

This propagator helps propagate tracing information from upstream services (such as AWS load balancers) to downstream services and handles conversion between the X-Ray trace id format and OpenTelemetry span contexts.

Checklist

Complete the checklist (and note appropriate exceptions) before a final PR is raised.

• Changes are compatible[^1]
• Documentation[^2] completed
• Performance impact assessed and acceptable
• Tests added and passing[^3]
  • Unit Tests
  • Integration Tests
  • Manual Tests

Exceptions

Note any exceptions here

Notes

[^1]. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.
[^2]. Configuration is an important part of many changes. Where applicable please try to document configuration examples.
[^3]. Tick whichever testing boxes are applicable. If you are adding Manual Tests:
- please document the manual testing (extensively) in the Exceptions.
- please raise a separate issue to automate the test and label it (or ask for it to be labeled) as manual test

[abernix]

Thanks for opening this. I actually came across another issue about this today and finally got around to leaving my comment on it. Maybe you could respond there? #3445 (comment)

Other than that, one comment within here, though as my question on the other issue will elude to, I'm curious if this could just be done with the existing "custom header" option that exists and how this differs, in practice.

Thanks again!

[abernix]

(compliant with opentracing)

I'm actually curious what this comment means (even on the other options). Is it compatible? What makes it so?

[scottmace]

I think that It means that the format is compatible with the OpenTelemetry OTLP exporter/collector.

[abernix]

"OpenTelemetry" makes sense, but I was more curious about "OpenTracing" (which is different, as I understand it).

However, your uncertainty here is totally fine. I only asked because I thought maybe you'd perhaps made understanding of it already. 😄

[scottmace]

Ah, yeah. It looks like OpenTracing was merged into OpenTelemetry. Perhaps the comments should be updated.

[apollo-cla]

@scottmace: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[router-perf]

CI performance tests

• xxlarge-request - Stress test with 100 MB request payload
• step - Basic stress test that steps up the number of users over time
• events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• events - Stress test for events with a lot of users and deduplication ENABLED
• large-request - Stress test with a 1 MB request payload
• const - Basic stress test that runs with a constant number of users
• no-graphos - Basic stress test, no GraphOS.
• reload - Reload test over a long period of time at a constant rate of users
• step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• xlarge-request - Stress test with 10 MB request payload
• events_big_cap_high_rate - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity

[abernix]

Note that I think the tests are failing because of the need to commit the changes after reviewing snapshot changes with cargo insta test. (You'd have to cargo install cargo-insta first, to use cargo insta test)

[bnjjj]

@scottmace Thanks ! It looks good! Sorry for the delay, could you generate a small changeset for that pr ? Using cargo xtask changeset create please