Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ECS] Addition - http.request.header.bytes & http.response.header.bytes #2280

Open
ScottElastic opened this issue Sep 26, 2023 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@ScottElastic
Copy link

Please fill in the following sections describing your proposed changes: -->
Ref: https://www.elastic.co/guide/en/ecs/current/ecs-http.html

Today, ECS has 2 fields for http request size:

http.request.body.bytes - body size in bytes
http.request.bytes - header+body size in bytes

It would be beneficial to have a field dedicated to the size of the headers as well, for ex:

http.request.header.bytes - header size in bytes

similarly for
http.response.header.bytes

To have more accurate detailed information on the http request without requiring math to be done by the end user.

@ScottElastic ScottElastic added the enhancement New feature or request label Sep 26, 2023
@jamiehynds
Copy link
Contributor

@ScottElastic have you come across any sample logs whereby the bytes values are exposed and thus could easily be mapped to these proposed fields? or would there be some calculations required in order to populate the fields?

@ebeahan any thoughts on these proposed fields?

@trisch-me
Copy link
Contributor

@ScottElastic do you have concrete examples where we would use this data or how to get this data?
I also suggest to put this kind of question into Otel repo as we are donating ECS to the Otel so would be great to have everything in 1 place.
If you have already use cases I can help to make a PR into otel community

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants