fix: properly inform cloud endpoints about the snappy compression #261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When using Grafana Agent with a logging backend other than Loki, we need to inform that backend about the payloads being compressed using snappy. Loki knows this is the case implicitly, but a third-party won't.
Solution
Add a
Content-Encoding
header to all outgoing requests.Context
This is useful when integrating with, for instance, Vector or Logstash, as they otherwise have no way of knowing about the encoding/compression.
Testing Instructions
Release Notes
Properly advertise snappy compression when using the cloud integrator