870627fbed
Currently Prometheus will always request gzip compression from the target when sending scrape requests. HTTP compression does reduce the amount of bytes sent over the wire and so is often desirable. The downside of compression is that it requires extra resources - cpu & memory. This also affects the resource usage on the target since it has to compress the response before sending it to Prometheus. This change adds a new option to the scrape job configuration block: enable_compression. The default is true so it remains the same as current Prometheus behaviour. Setting this option to false allows users to disable compression between Prometheus and the scraped target, which will require more bandwidth but it lowers the resource usage of both Prometheus and the target. Fixes #12319. Signed-off-by: Łukasz Mierzwa <l.mierzwa@gmail.com> |
||
|---|---|---|
| .. | ||
| alerting_rules.md | ||
| configuration.md | ||
| https.md | ||
| index.md | ||
| recording_rules.md | ||
| template_examples.md | ||
| template_reference.md | ||
| unit_testing_rules.md | ||