Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit c56dc5c

Browse files
committed
Remove paragraphs divisions
1 parent b12e18a commit c56dc5c

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

alerts-detectors-notifications/slo/custom-metric-scenario.rst

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,11 +25,7 @@ From the :guilabel:`Detectors & SLOs` page, Kai configures the SLI and sets up a
2525
G = data('synthetics.run.count', filter=filter('test', 'Monitoring Services - Emby check') and filter('success', 'true'))
2626
T = data('synthetics.run.count', filter=filter('test', 'Monitoring Services - Emby check'))
2727
28-
Kai defines variables ``G`` and ``T`` as two streams of ``synthetics.run.count`` metric time series (MTS) measuring the health of requests sent to the Emby service.
29-
30-
To distinguish between the two data streams, Kai applies an additional filter on the ``success`` dimension in the definition for ``G``. This filter queries for a specific collection of MTS that track successful requests for the Emby service.
31-
32-
In Kai's SignalFlow program, ``G`` is a data stream of good events and ``T`` is a data stream of total events.
28+
Kai defines variables ``G`` and ``T`` as two streams of ``synthetics.run.count`` metric time series (MTS) measuring the health of requests sent to the Emby service. To distinguish between the two data streams, Kai applies an additional filter on the ``success`` dimension in the definition for ``G``. This filter queries for a specific collection of MTS that track successful requests for the Emby service. In Kai's SignalFlow program, ``G`` is a data stream of good events and ``T`` is a data stream of total events.
3329

3430
.. image:: /_images/images-slo/custom-metric-slo-scenario.png
3531
:width: 100%

0 commit comments

Comments
 (0)