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
configuration.md	docs: Correct and clarify histogram bucket and resolution limits	2024-07-18 12:30:55 +02:00
https.md
index.md
recording_rules.md	Feature: Allow configuration of a rule evaluation delay (#14061)	2024-05-30 11:49:50 +01:00
template_examples.md
template_reference.md
unit_testing_rules.md