Forward incoming HTTP Request ID to remote services when using http.send

[kotyara85]

It looks like OPA doesn't honor x-request-id header at this moment
It would be great if it did, because that would give an ability to run E2E traces in case if http.send is involved
Thanks

[srenatus]

Can you please elaborate on your expectations? Should the request ID header become part of the response, or part of the open telemetry spans, or be used in decision logs...? What is you're checking in your E2E traces?

[kotyara85]

Yeah,
for example:
serviceA -> OPA -> serviceB

serviceA adds x-request-id header
this header would be exposed as reqId in opa info log and passed down to serviceB as x-request-id header

This way you can see one call across all the systems

Thanks

[srenatus]

Ah. So concretely, you're expecting the header to be sent along with http.send calls to remote services.

[kotyara85]

Ah. So concretely, you're expecting the header to be sent along with http.send calls to remote services.

Yeah

[kotyara85]

@srenatus it would be also beneficial to add reqId to logs

[anderseknert]

@kotyara85 did you check out the open telemetry integration?

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[anderseknert]

With the Open Telemetry support and #5196, I'm not sure this is needed. Let's re-open this if so.