Should server-timing env var be renamed to not mention "server timing"

[owais]

We are returning trace context in an HTTP response header. The header we use today is Server-Timing because of browser compatibility. In future, this header will likely change as W3C spec for trace response headers matures. As such we should not use the term "server timing" in configuration, documentation (except to clarify which header is used) and code, and instead, use "trace response". For example, the env var to enable or disable the feature should be SPLUNK_TRACE_RESPONSE_HEADER_ENABLED instead of SPLUNK_CONTEXT_SERVER_TIMING_ENABLED. In future, any move to a different header will be smoother if we do this.

[mateuszrzeszutek]

I agree, that seems to be a better name.

[pellared]

Is it something that can be proposed to OTel specs?

[owais]

It will be at some point once this proposal is accepted. https://w3c.github.io/trace-context/#trace-context-http-response-headers-format

[ghost]

Seems that everybody agree to scrap this name in this context :)

[pellared]

Resolved per #32