-
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
loki structured metadata not sent unless using snappy
compression
#21443
Comments
Thanks for filing this @victorserbu2709 including the details about the request payload. Could you try setting If that is the case, we should make that clearer in the docs and/or make it explicit error to configure cc/ @maxboone since you implemented this support |
Thank you for your quick response @jszwedko. |
I see that there is support for it with the JSON API by adding the object at the end of the log line. I'll see if I can open an MR with that tomorrow. Gave it a shot, but building for unit tests keep running out of memory, so will have to try on another machine tomorrow. |
snappy
compression
That would be great 🙏 Much simpler than trying to document that the option can only be used with snappy/protobuf. It could be useful to deprecate and remove the old JSON API though. I'm unsure it it offers anything that the protobuf API doesn't 🤔 |
A note for the community
Problem
I tried to use structured metadata with loki sink but i observed that these are not sent.
Simple replication:
This is the http body that is receive by nginx proxy
i tried with vector rpm 0.41.0 and also with nighly build
Configuration
Version
vector 0.42.0 (x86_64-unknown-linux-gnu 51dcf8d 2024-10-06 04:01:48.303006361)
Debug Output
The text was updated successfully, but these errors were encountered: