-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fluent source ack wrong format #17427
Labels
Comments
This was referenced May 17, 2023
Just noting that I also confirmed this behavior with
|
Closed by #17407 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A note for the community
Problem
As mentioned in #7533 (comment), the ACK format returned by the fluent source is not understood by fluent-bit, and generates an error:
[error] [output:forward:forward.0] ACK response not MAP (type:2)
Indeed, when the ack was implemented, #10176 mentioned that the ack format was not very clear, and was implemented as plain JSON, while in fact fluent-bit expects a msgpack format.
The issue as initially described in #7533 (comment):
Hello. Yes, I have some problems.
I using Vector as an aggregator and fluent-bit as a log collector, but in fluent-bit logs, I see errors like this:
Vector deployed via Helm chart version: 0.20.1 with these options:
Vector configuration is:
fluent-operator deployed via Helm chart 2.2.0, also tried 2.1.0
If you need more details, I can provide it.
Thank you
Configuration
No response
Version
0.30.0
Debug Output
No response
Example Data
No response
Additional Context
No response
References
#10176
#7533
The text was updated successfully, but these errors were encountered: