X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=hdmisdi.rst;h=f6f032cf48a29df3c27cb9e6a4b8359a2242d6d2;hb=1eec4ef47957c81d445c4b104e56ba2d8917d267;hp=30fc5eef5256f8222b1d09cf782a4dc05226014e;hpb=d9f1278097e427e8ba2ac4889e08568b3696843a;p=nageru-docs

diff --git a/hdmisdi.rst b/hdmisdi.rst
index 30fc5ee..f6f032c 100644
--- a/hdmisdi.rst
+++ b/hdmisdi.rst
@@ -196,6 +196,12 @@ lowest and highest will be printed. Do note that the measurement is still done
 over a single *output* frame; it is *not* a measurement over the last 100
 output frames, even though the statistics are only printed every 100th.
 
+For more precise measurements, you can use Prometheus metrics to get percentiles
+for all of these points, which will measure over all frames (over a one-minute
+window). This yields more precise information than sampling every 100 frames,
+but setting up Prometheus and a graphic tool is a bit more work, and usually not
+worth it for simple measurement. For more information, see :doc:`monitoring`.
+
 Another trick that can be useful in some situations is *looping* your signal,
 ie., connecting your output back into your input. This allows you to measure
 delays that don't happen within Nageru itself, like any external converters,
@@ -203,7 +209,7 @@ delays in the input driver, etc.. (It can also act as a sanity check to make
 sure your A/V chain passes the signal through without quality degradation,
 if you first set up a static picture as a signal and then switch to the loop
 input to verify that the signal stays stable without color e.g. shifts [#]_.
-See the section on :ref:`the frame analyzer <analyzer>` for other ways of
+See the section on :doc:`the frame analyzer <analyzer>` for other ways of
 debugging signal integrity.)
 
 For this, the *timecode output* is useful; you can turn it on from the Video