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

Support dynamic placeholder for out_http headers parameter #3237

Closed
davidbhoward opened this issue Jan 28, 2021 · 1 comment · Fixed by #3241
Closed

Support dynamic placeholder for out_http headers parameter #3237

davidbhoward opened this issue Jan 28, 2021 · 1 comment · Fixed by #3241
Assignees

Comments

@davidbhoward
Copy link

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.

Is your feature request related to a problem? Please describe.

Today I can't use dynamic headers for out_http plugin.

Describe the solution you'd like

We need the ability for headers to be dynamic in nature-based upon values inside the record. Today they can only be strings, but the goal would be to do something like header X-Custom-Host:${$.kubernetes.host},X-Custom-Datacenter:${$.datacenter}

Describe alternatives you've considered

I have tried all configuration options I could think with no luck. After exhausting all options, I finally reached out to the community and got a response from @repeatedly saying:

Currently, out_http's headers parameter doesn't support dynamic placeholder.
For it, we need to add headers_from_record like parameter with buffer placeholder.

Additional context

The question was posted on the Fluentd Google Group with the subject, "out_http headers not dynamic".

repeatedly added a commit that referenced this issue Feb 2, 2021
Signed-off-by: Masahiro Nakagawa <repeatedly@gmail.com>
@repeatedly repeatedly self-assigned this Feb 2, 2021
repeatedly added a commit that referenced this issue Feb 3, 2021
out_http: Add headers_from_placeholders. fix #3237
@davidbhoward
Copy link
Author

Thank you, @repeatedly, for doing this so quickly. We are already using it and it is working very well. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants