PB-1524: Renamed http request and response headers to header for OTEL compatibility #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ltflb-bgdi
changed the title
ltflb-bgdi
changed the base branch from
master
to
feat_pb_2146_otel_tracing_fields
ltflb-bgdi
force-pushed
the
feat_pb_1524_http_header
branch
from
fe1d0b4 to
b391160
Compare
ltflb-bgdi
force-pushed
the
feat_pb_1524_http_header
branch
from
b391160 to
17e6cf4
Compare
KeeTraxx
approved these changes
Dec 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since there are no official ECS fields for http headers we implemented them our way, based on common sense at the time of implementation. Since OTEL has a semconv for headers, we can switch our integrations to make these fields compatible. As a first step, the old
http.<request|response>.headers.<key>fields are renamed tohttp.<request|response>.header.<key>. Once this is done on all stages, we may rename the fields in the services directly.Review note: Since multiple datastreams are affected by the change, I re-generated all expected files. Updated timestamps can be ignored. As well, with a newer elastic-package versions, the json output seems now alphabetically sorted.