http: Separate whitelist/blacklist for propagation

[dobesv]

Is your feature request related to a problem? Please describe.

I have third-party services whose response times I would like to trace but where I don't want to propagate the trace parent ID to.

In general I don't see any value in sending the trace header to a third party, but specifically the header injection requests to services may cause some issues or conflicts, such as if headers are part of a authorizing signature calculation or the other service itself uses the same header for trace propagation but their telemetry database is separate from our own.

Describe the solution you'd like

Currently you can tell the plugin to ignore a set of URL patterns, and if you do that then matching URLs are not traced and no propagation headers are added.

It would be nice to have a second list of URL patterns where propagation is skipped but tracing is still applied.

Describe alternatives you've considered

I can disable all tracing and propagation for URLs that are problematic, this works but I lose some information about where the time is going if an operation uses an external service.

Additional context

• Instrumentation breaks some AWS S3 requests lightstep/otel-launcher-node#26
• https://stackoverflow.com/questions/64693442/wrong-aws-request-signature-caused-by-opentelemetry-https-plugin