You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And it works, but when I tried switching to file based buffer instead of memory based I get following errors on aggregators: 2022-06-24 14:01:00 +0000 [warn]: #0 failed to flush the buffer. retry_times=6 next_retry_time=2022-06-24 14:02:11 +0000 chunk="5e22f201e52be67145632a6d34f81fdb" error_class=URI::InvalidURIError error="bad URI(is not URI?): \"http://172.19.0.107:3000/api/${tag}\"".
Suddenly it stopped replacing placeholders.
And I'm wondering whether this is a feature (similar to out_file plugin description referenced below 1) or is it really a bug.
I somebody wonders, that's the config that is not working with error shown above:
It seems that same applies to file output. When used with buf_file it doesn't handle placeholders properly and you get paths like that: /opt/bitnami/fluentd/logs/buffers/fallback/${tag}.log
Addition 2.
I've found a description probably related to this situation in out_file plugin
I can see files but placeholders are not replaced, why?
You see an intermediate buffer file, not the output result. The placeholders are replaced during flush buffers.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've just encountered an issue with placeholders and the
buf_file
plugin.My output config looks something like that:
And it works, but when I tried switching to file based buffer instead of memory based I get following errors on aggregators:
2022-06-24 14:01:00 +0000 [warn]: #0 failed to flush the buffer. retry_times=6 next_retry_time=2022-06-24 14:02:11 +0000 chunk="5e22f201e52be67145632a6d34f81fdb" error_class=URI::InvalidURIError error="bad URI(is not URI?): \"http://172.19.0.107:3000/api/${tag}\""
.Suddenly it stopped replacing placeholders.
And I'm wondering whether this is a feature (similar to
out_file
plugin description referenced below 1) or is it really a bug.I somebody wonders, that's the config that is not working with error shown above:
Addition 1.
It seems that same applies to file output. When used with
buf_file
it doesn't handle placeholders properly and you get paths like that:/opt/bitnami/fluentd/logs/buffers/fallback/${tag}.log
Addition 2.
I've found a description probably related to this situation in
out_file
pluginFootnotes
https://docs.fluentd.org/output/file#:~:text=You%20see%20an%20intermediate%20buffer%20file%2C%20not%20the%20output%20result.%20The%20placeholders%20are%20replaced%20during%20flush%20buffers. ↩
Beta Was this translation helpful? Give feedback.
All reactions