Description:
Envoy currently enforces specific format of x-request-id header, and piggybacks tracing decisions into it.
However this approach does not play well with existing setups, which already heavily use both request ids and tracing, and rely on transmission of this data in different form (e.g. using explicit distinct headers for tracing-related metadata).

In short we would like to have an ability to use Envoy's tracing configuration (sample ratio, x-force-tracing header, skipping health checks, statistics, etc) with different data format.

Is it reasonable to make this behavior configurable, e.g. by ability to create native extensions which would override behavior of Envoy::UuidUtils?

Relevant Links: