prometheus/docs
1
0
Fork 0
mirror of https://github.com/prometheus/docs.git synced 2026-02-05 15:45:27 +01:00
Code Issues Releases Activity

chore(histogramspec): update due to test framework change

Browse Source 
Follow up https://github.com/prometheus/prometheus/pull/15995

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
This commit is contained in:
György Krajcsovits
2025-05-08 13:13:26 +02:00
parent db2b39804c
commit 72cec19681
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
content/docs/specs/native_histograms.md
View File

@@ -2045,15 +2045,14 @@ histogram sample notation is complex and explained in the [documentation for
rules unit
testing](https://prometheus.io/docs/prometheus/latest/configuration/unit_testing_rules/#series).
There is an alternative `load` command called `load_with_nhcb`, which converts
classic histograms to NHCBs and loads both the float series of the classic
histogram as well as the NHCB series resulting from the conversion.
In the unit test framework there is an alternative `load` command called
`load_with_nhcb`, which converts classic histograms to NHCBs and loads both the
float series of the classic histogram as well as the NHCB series resulting from
the conversion.
Not specific to native histograms, but very useful in their context, are the
`eval_info` and `eval_warn` keywords that expect the evaluation to result in at
least one info-level annotation or at least one warn-level annotation,
respectively. It is currently neither possible to test for the presence of
annotations of both levels nor to test for specific annotations.
Not specific to native histograms, but very useful in their context, is the
`expect` keyword in the unit test framework that can define expectations about
the info- and warn-level annotations.
### Optimizations