Skip to content
New issue

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

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

Already on GitHub? # to your account

Support boolean flag to retain HTTP headers #57

Closed
jmkgreen opened this issue Aug 1, 2016 · 3 comments
Closed

Support boolean flag to retain HTTP headers #57

jmkgreen opened this issue Aug 1, 2016 · 3 comments

Comments

@jmkgreen
Copy link

jmkgreen commented Aug 1, 2016

Looks like there are a few fields recorded by this plugin that we have no desire to keep in our storage and will therefore have to write filters to to discard them.

It would be nice to see a flag named retain_http_headers which could be set to true by default for backward compatibility reasons. When false these headers are simply not populated or are automatically filtered out.

@magnusbaeck
Copy link

magnusbaeck commented Sep 25, 2016

I suggest the fields are stored under @metadata, similar to how the rabbitmq input deals with message metadata. This is actually also suggested in #10.

@ebuildy
Copy link
Contributor

ebuildy commented May 9, 2018

#68 should do the trick

@jsvd
Copy link
Member

jsvd commented May 11, 2018

solved by #68

@jsvd jsvd closed this as completed May 11, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants