Elaborate on the SignalFlow program example in the scenario doc

Author: trangl-splunk

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

@@ -17,42 +17,26 @@ Use custom metric as service level indicator (SLI)
 
 From the :guilabel:`Detectors & SLOs` page, Kai configures the SLI and sets up a target for their SLO. Kai follows these steps: 
 
-#. Kai wants to use custom metrics as the system health indicators, so they select the :guilabel:`Custom metric` from the :guilabel:`Metric type` menu.
+#. Kai wants to use a Synthetics metric as the system health indicators, so they select the :guilabel:`Custom metric` from the :guilabel:`Metric type` menu.
 #. Kai enters following into the SignalFlow editor:
 
       .. code-block:: python
 
           G = data('synthetics.run.count', filter=filter('test', 'Monitoring Services - Emby check') and filter('success', 'true'))
           T = data('synthetics.run.count', filter=filter('test', 'Monitoring Services - Emby check'))
 
-   While Kai uses the same metric name for both the ``G`` and ``T`` variables, they use the ``success`` dimension to count the number of successful requests for the Emby service on the Buttercup Games website.
+   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.
 
       .. image:: /_images/images-slo/custom-metric-slo-scenario.png
           :width: 100%
           :alt: This image shows Kai's SLO configuration using the ``synthetics.run.count`` metric and appropriate filters.
 
-    ..     :header-rows: 1
-    ..     :widths: 10 20 30 40
-
-    ..     * - Field
-    ..       - SignalFlow editor
-    ..       - Filters
-    ..       - Description 
-
-    ..     * - :guilabel:`Good events (numerator)`
-    ..       - :strong:`synthetics.run.count`
-    ..       - Kai adds the following filters for this metric:
-            
-    ..           * :strong:`test = Emby check`
-    ..           * :strong:`success = true`
-    ..       - Kai uses the :strong:`success = true` filter to count the number of successful requests for the Emby service on the Buttercup Games website.
 
-    ..     * - :guilabel:`Total events (denominator)`
-    ..       - :strong:`synthetics.run.count`
-    ..       - Kai adds the following filter for this metric:
-
-    ..           * :strong:`test = Emby check`
-    ..       - 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.
+#. Kai assigns ``G`` to the :guilabel:`Good events (numerator)` dropdown menu, and ``T`` to the :guilabel:`Total events (denominator)` dropdown menu.
 
 #. Kai enters the following fields to define a target for their SLO:
 
@@ -85,3 +69,5 @@ Learn more
 For more information about creating an SLO, see :ref:`create-slo`. 
 
 For more information about the Synthetics Browser test, see :ref:`browser-test`.
+
+For more information on SignalFlow, see :new-page:`Analyze data using SignalFlow <https://dev.splunk.com/observability/docs/signalflow>` in the Splunk Observability Cloud Developer Guide.