prometheus/docs/configuration
beorn7 a6fa8a471c docs: Correct and clarify histogram bucket and resolution limits
Previously, the config doc suggested that scrapes are simply failed if
the bucket limit is exceeded. However, instead Prometheus first
attempts to reduce the resolution. This will succeed in almost all
non-pathological cases. However, in the rare case that it doesn't, the
scrape will be failed after all.

For the resolution limit AKA `native_histogram_min_bucket_factor`, the
logic is a bit different. Once the highest factor, i.e. schema -4, is
reached, the scrape will still succeed.

Signed-off-by: beorn7 <beorn@grafana.com>
2024-07-18 12:30:55 +02:00
..
alerting_rules.md Add sentence explaining what happens when the for clause is omitted (#12457) 2023-06-16 11:55:41 +01:00
configuration.md docs: Correct and clarify histogram bucket and resolution limits 2024-07-18 12:30:55 +02:00
https.md Update exporter-toolkit 2023-05-30 09:08:00 +02:00
index.md Consolidate configuration and rules docs in docs/configuration/ 2017-10-27 09:54:02 +02:00
recording_rules.md Feature: Allow configuration of a rule evaluation delay (#14061) 2024-05-30 11:49:50 +01:00
template_examples.md format markdown code block (#5594) 2019-05-25 11:28:50 +01:00
template_reference.md Support native histogram values in template functions 2024-03-26 22:30:01 +01:00
unit_testing_rules.md Set test group interval default to evaluation interval (#13011) 2023-10-20 21:32:46 +11:00