Skip to content

Commit d83ff77

Browse files
author
ada
committed
Updated wording
1 parent c82542e commit d83ff77

File tree

1 file changed

+28
-16
lines changed

1 file changed

+28
-16
lines changed

synthetics/test-status/test-status.rst

Lines changed: 28 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -37,20 +37,14 @@ Splunk Synthetics updates the current state of each test every time you load the
3737
:header-rows: 1
3838
:widths: 20, 80
3939

40-
* - :strong:`Current status`
40+
* - :strong:`Test state`
4141
- :strong:`Description`
4242

43-
* - Pending
44-
- Splunk Synthetic Monitoring is still retrieving the status of this test.
45-
46-
* - Available
47-
- The test is functioning properly. If the test is active, data is being collected at the set interval and can be viewed in the :guilabel:`Test History` page. If the test is paused, it can be unpaused and will resume collecting data.
43+
* - Active
44+
- The test is running. Data is being collected at the set interval. You can view this data on the :guilabel:`Test History` page.
4845

49-
* - No Data
50-
- The test isn't currently collecting data.
51-
52-
* - Failure
53-
- The test encountered a failure.
46+
* - Paused
47+
- The test is paused. To resume data collection, unpause it.
5448

5549

5650

@@ -59,11 +53,28 @@ View run status
5953

6054
The :guilabel:`Last run status` column displays the outcome of each test's last run.
6155

56+
.. list-table::
57+
:header-rows: 1
58+
:widths: 20, 80
59+
60+
* - :strong:`Last run status`
61+
- :strong:`Description`
62+
63+
* - Success
64+
- The last run succeeded.
65+
66+
* - Pending
67+
- Splunk Synthetics is still retrieving the run status.
68+
69+
* - Failed
70+
- The last run encountered a failure.
71+
72+
6273

6374
Single actions
6475
========================================================================================
6576

66-
To performm an action on a single test, select the more menu (|more|) in its rightmost column. Supported actions are play and pause.
77+
To perform an action on a single test, select the kabob menu (|more|) in its rightmost column. Supported actions are play and pause.
6778

6879

6980
Bulk actions
@@ -73,10 +84,11 @@ You can perform bulk actions on multiple tests simultaneously. Supported actions
7384

7485
To perform a bulk action on tests:
7586

76-
#. Select the tests to change by either:
87+
#. Select the tests to change by either:
7788

78-
* Selecting the checkbox next in the leftmost column of one or more tests
79-
* Selecting the checkbox in the table header. This checkbox selects all tests on the current page -- a maximum of 20 tests. You can scroll through the pages to select more tests. The maximum you can select at one time is 3000.
89+
* Selecting the checkbox next in the leftmost column of one or more tests.
90+
* Selecting the checkbox in the table header. This checkbox selects all tests on the current page -- a maximum of 20 tests. You can scroll through the pages to select more tests. The maximum you can select at one time is 500.
8091

8192
#. At the top of the table, select the desired action: :guilabel:`Play`, :guilabel:`Pause`, or :guilabel:`Delete`.
82-
If the entire bulk action succeeds, the :guilabel:`Test state` column displays the new state of each of the affected tests. If any part of the bulk action fails, the entire bulk action is cancelled and none of the tests are updated.
93+
If the entire bulk action succeeds, the :guilabel:`Test state` column displays the new state of each of the affected tests. If any part of the bulk action fails, the entire bulk action is cancelled and none of the tests are updated. For example, if the bulk action was to delete 400 tests and one deletion fails, none of the tests are deleted.
94+

0 commit comments

Comments
 (0)