Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit b113a4d

Browse files
Merge pull request #2597 from splunk/trangl-o11ydocs-6188-new-detector-list
New detector list view and tags feature
2 parents a272b66 + d1f359a commit b113a4d

File tree

8 files changed

+111
-49
lines changed

8 files changed

+111
-49
lines changed
124 KB
Loading
242 KB
Loading
63.4 KB
Loading

alerts-detectors-notifications/alerts-and-detectors/create-detectors-for-alerts.rst

Lines changed: 41 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Create detectors
2222

2323
The high-level steps for creating a detector are:
2424

25-
1. Choose :ref:`how to create the detector <how-to-create-detector>`.
25+
1. Decide :ref:`how you want to create the detector <how-to-create-detector>`.
2626

2727
2. Create :ref:`alert rules <build-rules>` to the detector to specify when to trigger alerts.
2828

@@ -35,8 +35,7 @@ There are several ways to create a detector.
3535

3636
* You can clone an existing detector if you have existing detectors that you want to modify. See :ref:`clone-detector`.
3737
* You can customize AutoDetect detectors. See :ref:`autodetect-customize`.
38-
* Start from the Detector tab to create detectors based on what you are currently viewing, such as a chart or the Infrastructure Navigator. See :ref:`create-detector-from-chart`.
39-
* Create a detector from a dashboard chart to preselect one of the chart signals as the signal to be monitored. See :ref:`create-detector-from-chart`.
38+
* Create a detector from one of the signals on the chart you're viewing. See :ref:`create-detector-from-chart`.
4039
* Create a detector from scratch. See :ref:`create-detector-from-scratch`.
4140
* Use the API to programmatically create detectors, instead of creating them through the user interface. See :ref:`create-via-api`.
4241

@@ -45,7 +44,7 @@ There are several ways to create a detector.
4544
Clone an existing detector
4645
-------------------------------------------------------------------
4746

48-
You can see a list of existing detectors on the :guilabel:`Detectors` tab under :guilabel:`Detectors & SLOs`.
47+
You can see a list of existing detectors on the :guilabel:`Detectors` tab of the :guilabel:`Detectors & SLOs` page.
4948

5049
1. Look for a detector that is similar to the detector you want to create.
5150
2. Select the detector.
@@ -62,18 +61,18 @@ If there is a chart that monitors a signal that you want to alert on, you can us
6261

6362
Follow these steps to create the detector:
6463

65-
#. Select the bell icon on a chart to open the :strong:`Detector` menu.
64+
#. Select the bell icon on a chart.
6665
#. Select :menuselection:`New detector from chart`.
6766
#. To continue, see :ref:`build-rules`.
6867

69-
After you create a detector from a chart, a :ref:`link to the new detector<link-detector-to-chart>` is automatically added to the chart.
68+
After you create a detector from a chart, the detector is automatically linked to the chart.
7069

7170
.. _create-detector-from-scratch:
7271

7372
Create a detector from scratch
7473
-------------------------------------------------------------------
7574

76-
To create a new detector for Infrastructure or Custom Metrics from scratch, you can either select :guilabel:`New Detector` under :guilabel:`Detectors & SLOs`, or select :menuselection:`Custom Detector` from the create menu on the navigation bar. Enter a detector name and then select :guilabel:`Create Alert Rule` to proceed to the alert rule builder. For instructions on building the rule, see :ref:`build-rules`.
75+
To create a new detector from scratch, you can either select :guilabel:`Create detector` on the :guilabel:`Detectors & SLOs` page, or select :menuselection:`Detector` from the create menu on the navigation bar. Enter a detector name and then select :guilabel:`Create alert rule` to proceed to the alert rule builder. For instructions on building the rule, see :ref:`build-rules`.
7776

7877
.. _create-via-api:
7978

@@ -86,8 +85,7 @@ Using the API to create a detector provides a number of capabilities that are no
8685

8786
- For information on using the UI to edit detectors created using the API, see :ref:`v2-detector-signalflow`.
8887

89-
.. note:: If a detector display includes a SignalFlow tab, you are viewing a detector created programmatically using the :new-page:`Splunk Observability Cloud Detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`. If you are familiar with that API, you can use the detector display to
90-
view and edit the detector code and make changes to the detector rules.
88+
.. note:: If a detector display includes a :guilabel:`SignalFlow` tab, you are viewing a detector created programmatically using the :new-page:`Splunk Observability Cloud detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`. If you are familiar with that API, you can use the detector display to view and edit the detector code and make changes to the detector rules.
9189

9290

9391
.. _build-rules:
@@ -140,7 +138,7 @@ If the detector has multiple signals, select what signal you want to alert on.
140138
Select alert conditions
141139
-------------------------------------------------------------------
142140

143-
On the :strong:`Alert condition` tab, select the type of condition that triggers an alert. If you want to create compound conditions using AND or OR operators on the Alert settings tab, you must use the Custom Threshold condition. This applies whether you are monitoring a single signal or multiple signals.
141+
On the :strong:`Alert condition` tab, select the type of condition that triggers an alert. If you want to create compound conditions using ``AND`` or ``OR`` operators on the :guilabel:`Alert settings` tab, you must use the Custom Threshold condition. This applies whether you are monitoring a single signal or multiple signals.
144142

145143
See :ref:`condition-reference` for the list of the available built-in alert conditions for Infrastructure Monitoring and Custom Metrics detectors.
146144

@@ -161,7 +159,7 @@ In the chart, use a preview of the alerts that are triggered based on the settin
161159

162160
After you have specified settings for triggering alerts, continue to the next tab to create a message that is sent when the alert is triggered.
163161

164-
.. note:: If you don't see the Alert settings tab, you are viewing a detector that was created using the API; alert settings are defined in the :ref:`SignalFlow tab<v2-detector-signalflow>`.
162+
.. note:: If you don't see the :guilabel:`Alert settings` tab, you are viewing a detector that was created using the API; alert settings are defined in the :ref:`SignalFlow tab<v2-detector-signalflow>`.
165163

166164
.. _alert-message:
167165

@@ -267,9 +265,9 @@ The following table explains different types of email notifications:
267265
Activate
268266
-------------------------------------------------------------------
269267

270-
On the :strong:`Activate` tab you see a summary of the detector settings you specified. Review the summary and make any necessary changes in the associated tabs, then name the rule; by default, the rule name is the same as the detector name. The rule name is displayed on the Alerts page and in notifications.
268+
On the :guilabel:`Activate` tab you see a summary of the detector settings you specified. Review the summary and make any necessary changes in the associated tabs, then name the rule. By default, the rule name is the same as the detector name. The rule name is displayed on the :guilabel:`Alerts` page and in notifications.
271269

272-
Select :guilabel:`Activate Alert Rule` to save the detector and begin monitoring the specified signal. After you activate the detector, the :strong:`Alert Rules` tab of the detector is displayed, showing the signal you selected and a summary of the rule you built. You can edit the detector name; the text you enter here is displayed as the detector name on the :guilabel:`Detectors` tab under :guilabel:`Detectors & SLOs`. You can also provide additional descriptive text below the name, for example, to clarify the purpose of the detector for others.
270+
Select :guilabel:`Activate Alert Rule` to save the detector and begin monitoring the specified signal. After you activate the detector, the :guilabel:`Alert Rules` tab of the detector is displayed, showing the signal you selected and a summary of the rule you built. You can edit the detector name; the text you enter here is displayed as the detector name on the :guilabel:`Detectors` tab under :guilabel:`Detectors & SLOs`. You can also provide additional descriptive text to clarify the purpose of the detector for others.
273271

274272

275273
.. note:: If you make any changes to the detector name or description, select the :guilabel:`Save` button. If you select the :strong:`Close` button without saving, your changes will be lost.
@@ -283,9 +281,9 @@ Select :guilabel:`Activate Alert Rule` to save the detector and begin monitoring
283281
Edit detectors through the SignalFlow tab
284282
----------------------------------------------------------------------------------
285283

286-
.. note:: This section assumes you are familiar with the :new-page:`Splunk Observability Cloud Detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`.
284+
.. note:: This section assumes you are familiar with the :new-page:`Splunk Observability Cloud detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`.
287285

288-
If you are modifying a detector that was created using the API, you can add and edit detector rules using the SignalFlow tab. The SignalFlow program text replaces the Alert signal, Alert condition, and Alert settings tabs that are used when creating and editing detectors using the UI.
286+
If you are modifying a detector that was created using the API, you can add and edit detector rules using the :guilabel:`SignalFlow` tab. The SignalFlow program text replaces the :guilabel:`Alert signal`, :guilabel:`Alert condition`, and :guilabel:`Alert settings` tabs that are used when creating and editing detectors using the UI.
289287

290288
Every ``publish`` statement in a SignalFlow ``detect`` statement corresponds to a rule on the Alert Rules tab. The label you enter inside the ``publish`` block is displayed next to the number of active alerts displayed on the Alert Rules tab.
291289

@@ -346,8 +344,8 @@ On the :guilabel:`Alert Rules` tab of a detector, you can use the actions menu (
346344

347345
.. _disable-enable-rules:
348346

349-
Activate/deactivate alert rules
350-
---------------------------------
347+
Activate or deactivate alert rules
348+
-------------------------------------
351349

352350
If a detector has multiple rules, such as different rules for different severity levels, you can specify which ones to activate or deactivate. Deactivating a rule prevents it from generating any events or sending any notifications. Use this option to decrease or increase the number of alerts the detector is triggering.
353351

@@ -367,10 +365,34 @@ Delete alert rules
367365

368366
Use this option to remove a rule from the detector.
369367

368+
.. _detector-tags:
369+
370+
Tag a detector
371+
=============================================================================
372+
373+
Use tags to indicate the state of a detector, its data source, or any other property you want to label. For example, you can tag a detector with ``prod`` to indicate that it monitors a production environment.
374+
375+
You can tag detectors from the list view. To see a list of detectors and add tags, do the following:
376+
377+
#. To open the list view, open the :guilabel:`Detectors & SLOs` page, then select the :guilabel:`Detectors` tab.
378+
#. Select the actions menu (|more|) for the detector you want to assign tags to.
379+
#. Select :guilabel:`Edit tags`.
380+
#. Enter tags for the detector. You can add no more than 20 tags per detector.
381+
#. Select :guilabel:`Save`.
382+
383+
Link teams to a detector
384+
=============================================================================
385+
386+
Link teams to a detector to indicate which team is responsible for the maintenance and monitoring of the detector. Teams associated with a detector can see the detector and its active alerts on the team's landing page.
387+
388+
To link teams to a detector, select the detector actions menu (|more|), either from the list view of the individual detector view, then select :guilabel:`Link to teams`. You can link no more than 20 teams to a detector.
389+
390+
.. note:: The list of teams linked to a detector is independent of notification settings. Associated teams don't automatically get notified of new alerts. To configure notifications, see :ref:`manage-notifications`.
391+
370392
.. _set-detector-permissions:
371393

372394
Set detector permissions
373395
=============================================================================
374396

375-
To protect detectors from being edited or deleted by other members of your organization, you can specify which users and teams have permissions for them.
376-
For more information, see :ref:`detector-manage-permissions`.
397+
To protect detectors from being edited or deleted by other members of your organization, you can specify which users and teams have permissions for them. For more information, see :ref:`detector-manage-permissions`.
398+

alerts-detectors-notifications/alerts-and-detectors/detector-manage-permissions.rst

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To learn more about write permissions, see :ref:`about-write-permissions`.
2020

2121
If you want to get write permission for a detector, or if you want to modify permissions,
2222
first determine who already has permissions by displaying the :strong:`Permissions` list.
23-
You can then ask a user who has permission to add you to the permissions list.
23+
You need a user who has write permission to add you to the permissions list.
2424

2525
.. _display-write-permissions-detectors:
2626

@@ -45,10 +45,10 @@ for users or teams. To grant or revoke permissions for a detector, you need writ
4545

4646
.. _procedure-grant-write-permissions:
4747

48-
Grant write permissions for detectors
48+
Grant write permission for detectors
4949
---------------------------------------------------------
5050

51-
To grant write permissions for a detector, follow these steps:
51+
To grant write permission for a detector, follow these steps:
5252

5353
#. Display the permissions for the item by selecting the detector's actions menu (|more|) and selecting :guilabel:`Permissions`.
5454
#. To start using specific write permissions for a detector,
@@ -71,11 +71,8 @@ To revoke write permissions for a detector, follow these steps:
7171

7272
.. note:: Important
7373

74-
You can remove your own write permission from a detector.
75-
If you do this deliberately or by accident, and you're not an administrator,
76-
you can't grant yourself write permission again.
77-
Instead, you have to find someone else with write permission to grant you
78-
write permission.
74+
You can remove your own write permission from a detector. However, if you're not an administrator, you can't grant yourself write permission again.
75+
Instead, you have to find someone else with write permission to grant you write permission.
7976

8077

8178
.. _detector-action-table:

alerts-detectors-notifications/alerts-and-detectors/detector-options.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Detector options
99
.. meta::
1010
:description: How to set detector options in the Options tab.
1111

12-
The Options tab lets you specify some of the same settings that are available in the :ref:`Chart Options tab<chart-options-tab>` of a chart.
12+
The :guilabel:`Options` tab lets you specify some of the same settings that are available in the :ref:`Chart Options tab<chart-options-tab>` of a chart.
1313

1414

1515
Show events as lines

0 commit comments

Comments
 (0)