Skip to content

Commit 2d2961b

Browse files
authored
Merge pull request #2735 from splunk/adasplunk-O11YDOCS-7152
[O11YDOCS-7152] Update downtime config docs to clarify recurring edit…
2 parents eb102a9 + d9324ad commit 2d2961b

File tree

1 file changed

+20
-6
lines changed

1 file changed

+20
-6
lines changed

synthetics/test-config/syn-downtimes.rst

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ The best practice is to schedule a downtime configuration with a 15 to 30 minute
2828

2929
Schedule requirements:
3030

31-
* Downtimes configurations must be at least fifteen minutes long.
32-
* Downtimes configurations can be a maximum of one year in advance and one year in duration.
31+
* Downtime configurations must be at least fifteen minutes long.
32+
* Downtime configurations can be a maximum of one year in advance and one year in duration.
3333

3434
How to schedule a downtime configuration:
3535

@@ -41,15 +41,29 @@ How to schedule a downtime configuration:
4141
#. Select :guilabel:`Create`.
4242

4343

44-
When a recurring downtime configuration is active, you can't edit, delete, or extend it, but you can end it immediately. When a non-recurring downtime configuration is active, you can't edit or delete it, but you can extend its duration or end it immediately.
45-
46-
4744
Preview the downtime schedule
48-
----------------------------------------
45+
------------------------------------------------------------
4946

5047
If you selected a value other than :guilabel:`Does not repeat` in the :guilabel:`Recurrence` menu, the :guilabel:`Create a downtime configuration` form displays a preview of the first ten downtime configurations.
5148

5249

50+
Modify a downtime configuration
51+
============================================================
52+
53+
* Before a downtime configuration has run:
54+
55+
* If it's non-recurring you can edit or delete it.
56+
* If it's recurring you can edit it, but you can only delete it before its first run. Its status may still be displayed as :guilabel:`Scheduled`, but it's functionally locked after the first occurrence.
57+
* To delete a downtime configuration, select the :guilabel:`Delete` action from the vertical dot menu (|verticaldots|).
58+
59+
* While a downtime configuration is active:
60+
61+
* If it's non-recurring you can't edit or delete it, but you can extend it or end it immediately.
62+
* If it's recurring you can't edit, delete, or extend it, but you can end it immediately.
63+
64+
* After the first run of a downtime configuration, whether it's recurring or not, you can't delete or edit it.
65+
66+
5367
Mute alerts during downtime
5468
============================================================
5569

0 commit comments

Comments
 (0)