Skip to content

Commit b2bcb08

Browse files
author
ada
committed
Fix screenshot sizing
1 parent 666498f commit b2bcb08

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

synthetics/test-config/synth-alerts.rst

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In Synthetics, there are detectors to alert on metrics at the test level, at the
4141
| Examples: Send an alert on the three transaction-level metrics that Splunk Synthetic Monitoring captures (duration, requests, and size). See :ref:`transaction-level-detector` to learn more.
4242
4343

44-
Sample use case: Send an alert when a synthetic test fails
44+
Best practices for sending an alert when a synthetic test fails
4545
===============================================================
4646

4747
You can set up a detector while initially creating or editing a test, or from the results view for a particular test. A detector can track one or more synthetic tests.
@@ -69,10 +69,8 @@ In the detector dialog box, enter the following fields:
6969
#. Select :guilabel:`Activate`.
7070

7171
.. image:: /_images/synthetics/detector-one.png
72-
:width: 40%
73-
:alt: Screenshot showing the troubleshooting tab for a tile in the dashboard with an option to open the data in RUM or APM.
74-
75-
72+
:width: 100%
73+
:alt: Setting up a detector for failed tests.
7674

7775
Your detector is now set up to check for failed test runs every minute and to send an alert based on your settings in :guilabel:`Alert details`.
7876

0 commit comments

Comments
 (0)