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

Bug in http.request/response.header beats vs template name #8564

Closed
vbohata opened this issue Oct 4, 2018 · 3 comments
Closed

Bug in http.request/response.header beats vs template name #8564

vbohata opened this issue Oct 4, 2018 · 3 comments
Assignees
Labels
bug Metricbeat Metricbeat module Team:Integrations Label for the Integrations team

Comments

@vbohata
Copy link

vbohata commented Oct 4, 2018

There is a difference between templates and real event fields generated by metricbeat. According to doc and (https://github.com/elastic/beats/blob/99824df163863478d27688206e18ec27bc1b3ac5/metricbeat/module/http/json/json.go ... if I am not looking in wrong place) it generates field http.request.headers and http.response.headers. But in template there is http.request.header and http.response.header (without ending s). In fact it is not a problem, but it makes object definition here useless.

@ruflin
Copy link
Contributor

ruflin commented Oct 4, 2018

This indeed seems to be a bug. Thanks for raising. @sayden Could you have a look?

@sayden
Copy link
Contributor

sayden commented Oct 4, 2018

Sure @ruflin 😃

@sayden
Copy link
Contributor

sayden commented Dec 21, 2018

Fixed here #8585

@sayden sayden closed this as completed Dec 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Metricbeat Metricbeat module Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests

3 participants