Skip to content

Commit 9e39525

Browse files
author
Nils
authored
Update Watchdog monitor page with additional filters (DataDog#21625)
* Update Watchdog monitor page with additional filters * add images
1 parent 57e1047 commit 9e39525

File tree

4 files changed

+27
-3
lines changed

4 files changed

+27
-3
lines changed

content/en/monitors/types/watchdog.md

Lines changed: 27 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,16 +31,24 @@ In this section, choose between an APM, Infrastructure, or Logs alert:
3131

3232
An APM alert is created when Watchdog detects anomalous behavior on your system's services or their child resources.
3333

34-
{{< img src="/monitors/monitor_types/watchdog/watchdog-monitor-apm2.png" alt="Configuring a Watchdog Monitor on APM" style="width:80%;">}}
34+
{{< img src="/monitors/monitor_types/watchdog/watchdog-monitor-apm3.png" alt="Configuring a Watchdog Monitor on APM" style="width:80%;">}}
3535

3636
### Select sources {#select-sources-1}
3737

3838
Select the scope to be alerted on by configuring:
3939

40+
**1. Predefined selectors**
4041
* The type of Watchdog anomaly: Error Rates, Latency, Hits, or any APM alert
4142
* The value for APM primary tags (see the [Set primary tags to scope][1] page for instructions to configure APM primary and second primary tags)
4243
* The [APM service][2] (choose `Any services` to monitor all services)
4344
* The [APM resource][3] of a service (choose `*` to monitor all resources of a service)
45+
46+
**2. Additional filters**
47+
* Filter on any additional tag available on the Watchdog event (like `team` for example)
48+
* Boolean and wildcards are supported
49+
* Dimensions available on the predefined selectors should not be used in the additional filters
50+
51+
**3. Group By**
4452
* The dimensions you want to [group notifications by][4]
4553

4654
After your selections are made, the graph at the top of the monitor creation page displays the matching Watchdog events over the selected time frame.
@@ -52,14 +60,22 @@ After your selections are made, the graph at the top of the monitor creation pag
5260
{{% /tab %}}
5361
{{% tab "Infrastructure" %}}
5462

55-
{{< img src="/monitors/monitor_types/watchdog/watchdog-monitor-infra.png" alt="Configuring a Watchdog Monitor on Infrastructure" style="width:80%;">}}
63+
{{< img src="/monitors/monitor_types/watchdog/watchdog-monitor-infra-2.png" alt="Configuring a Watchdog Monitor on Infrastructure" style="width:80%;">}}
5664

5765
### Select sources {#select-sources-2}
5866

5967
Select the scope to be alerted on by configuring:
6068

69+
**1. Predefined selectors**
6170
* The Infrastructure integration to cover (select `Any Infrastructure alert` to cover them all). See the [Watchdog overview][1] for a full list of integrations covered by Watchdog infrastructure)
6271
* The Tags available for the selected integration
72+
73+
**2. Additional filters**
74+
* Filter on any additional tag available on the Watchdog event (like `team` for example)
75+
* Boolean and wildcards are supported
76+
* Dimensions available on the predefined selectors should not be used in the additional filters
77+
78+
**3. Group By**
6379
* The dimensions you want to [group notifications by][2]
6480

6581
After your selections are made, the graph at the top of the monitor creation page displays the matching Watchdog events over the selected time frame.
@@ -71,17 +87,25 @@ After your selections are made, the graph at the top of the monitor creation pag
7187

7288
A logs alert indicates that either a new pattern of error logs has been detected or that there has been an increase in an existing pattern of error logs.
7389

74-
{{< img src="/monitors/monitor_types/watchdog/log_anomaly_monitor-2.png" alt="The Watchdog monitor's edit page showing the alert category set to logs, alert type as log anomaly, env set to production, service set to ad-server, and the monitor's title is Anomaly Detected in Production Ad Server" style="width:55%;">}}
90+
{{< img src="/monitors/monitor_types/watchdog/log_anomaly_monitor-3.png" alt="The Watchdog monitor's edit page showing the alert category set to logs, alert type as log anomaly, env set to production, service set to ad-server, and the monitor's title is Anomaly Detected in Production Ad Server" style="width:55%;">}}
7591

7692
### Select sources {#select-sources-3}
7793

7894
Select the scope to be alerted on by configuring:
7995

96+
**1. Predefined selectors**
8097
* The environment (leave empty to alert on all environments). These values are derived from the `env` tag in your logs
8198
* The service (leave empty to alert on all services). These values are derived from the `service` [reserved attribute][2] in your logs
8299
* The log source (leave empty to alert on all sources). These values are derived from the `source` [reserved attribute][2] in your logs
83100
* The log status (leave empty to alert on all status). These values are derived from the `status` [reserved attribute][2] in your logs
84101
* The log anomaly type (`new Error` or `Spike in existing logs`) determines whether the anomaly describes a new pattern of error logs or an increase in an existing pattern of error logs
102+
103+
**2. Additional filters**
104+
* Filter on any additional tag available on the Watchdog event (like `team` for example)
105+
* Boolean and wildcards are supported
106+
* Dimensions available on the predefined selectors should not be used in the additional filters
107+
108+
**3. Group By**
85109
* The dimensions you want to [group notifications by][1]
86110

87111
After your selections are made, the graph at the top of the monitor creation page displays the matching Watchdog events over the selected time frame.
141 KB
Loading
152 KB
Loading
143 KB
Loading

0 commit comments

Comments
 (0)