You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: alerts-detectors-notifications/slo/custom-metric-scenario.rst
+29-24Lines changed: 29 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,31 +18,41 @@ Use custom metric as service level indicator (SLI)
18
18
From the :guilabel:`Detectors &SLOs` page, Kai configures the SLI and sets up a target for their SLO. Kai follows these steps:
19
19
20
20
#. Kai wants to use custom metrics as the system health indicators, so they select the :guilabel:`Custom metric` from the :guilabel:`Metric type` menu.
21
-
#. Kai enters the custom metrics they want to measure in the following fields:
21
+
#. Kai enters following into the SignalFlow editor:
T = data('synthetics.run.count', filter=filter('test', 'Monitoring Services - Emby check'))
27
+
28
+
While Kai uses the same metric name for both the ``G`` and ``T`` variables, they use the :strong:`success` dimension to count the number of successful requests for the Emby service on the Buttercup Games website.
:alt:This image shows Kai's SLO configuration using the ``synthetics.run.count`` metric and appropriate filters.
33
+
34
+
.. :header-rows: 1
35
+
.. :widths: 10 20 30 40
36
+
37
+
.. * - Field
38
+
.. - SignalFlow editor
39
+
.. - Filters
40
+
.. - Description
41
+
42
+
.. * - :guilabel:`Good events (numerator)`
43
+
.. - :strong:`synthetics.run.count`
44
+
.. - Kai adds the following filters for this metric:
35
45
36
-
* :strong:`test = Emby check`
37
-
* :strong:`success = true`
38
-
- Kai uses the :strong:`success = true` filter to count the number of successful requests for the Emby service on the Buttercup Games website.
46
+
.. * :strong:`test = Emby check`
47
+
.. * :strong:`success = true`
48
+
.. - Kai uses the :strong:`success = true` filter to count the number of successful requests for the Emby service on the Buttercup Games website.
39
49
40
-
* - :guilabel:`Total events (denominator)`
41
-
- :strong:`synthetics.run.count`
42
-
- Kai adds the following filter for this metric:
50
+
.. * - :guilabel:`Total events (denominator)`
51
+
.. - :strong:`synthetics.run.count`
52
+
.. - Kai adds the following filter for this metric:
43
53
44
-
* :strong:`test = Emby check`
45
-
- Kai uses the same metric name and the :strong:`test = Emby check` filter to track the same Synthetics Browser test. However, Kai doesn't include the :strong:`success = true` dimension filter in order to count the number of total requests for the Emby service on the Buttercup Games website.
54
+
.. * :strong:`test = Emby check`
55
+
.. - Kai uses the same metric name and the :strong:`test = Emby check` filter to track the same Synthetics Browser test. However, Kai doesn't include the :strong:`success = true` dimension filter in order to count the number of total requests for the Emby service on the Buttercup Games website.
46
56
47
57
#. Kai enters the following fields to define a target for their SLO:
48
58
@@ -64,11 +74,6 @@ From the :guilabel:`Detectors & SLOs` page, Kai configures the SLI and sets up a
64
74
65
75
#. Kai subscribes to receive an alert whenever there is a breach event for the SLO target.
0 commit comments