You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/monitors/types/watchdog.md
+27-3Lines changed: 27 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,16 +31,24 @@ In this section, choose between an APM, Infrastructure, or Logs alert:
31
31
32
32
An APM alert is created when Watchdog detects anomalous behavior on your system's services or their child resources.
33
33
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%;">}}
35
35
36
36
### Select sources {#select-sources-1}
37
37
38
38
Select the scope to be alerted on by configuring:
39
39
40
+
**1. Predefined selectors**
40
41
* The type of Watchdog anomaly: Error Rates, Latency, Hits, or any APM alert
41
42
* 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)
42
43
* The [APM service][2] (choose `Any services` to monitor all services)
43
44
* 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**
44
52
* The dimensions you want to [group notifications by][4]
45
53
46
54
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
52
60
{{% /tab %}}
53
61
{{% tab "Infrastructure" %}}
54
62
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%;">}}
56
64
57
65
### Select sources {#select-sources-2}
58
66
59
67
Select the scope to be alerted on by configuring:
60
68
69
+
**1. Predefined selectors**
61
70
* 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)
62
71
* 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**
63
79
* The dimensions you want to [group notifications by][2]
64
80
65
81
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
71
87
72
88
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.
73
89
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%;">}}
75
91
76
92
### Select sources {#select-sources-3}
77
93
78
94
Select the scope to be alerted on by configuring:
79
95
96
+
**1. Predefined selectors**
80
97
* The environment (leave empty to alert on all environments). These values are derived from the `env` tag in your logs
81
98
* The service (leave empty to alert on all services). These values are derived from the `service`[reserved attribute][2] in your logs
82
99
* The log source (leave empty to alert on all sources). These values are derived from the `source`[reserved attribute][2] in your logs
83
100
* The log status (leave empty to alert on all status). These values are derived from the `status`[reserved attribute][2] in your logs
84
101
* 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**
85
109
* The dimensions you want to [group notifications by][1]
86
110
87
111
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.
0 commit comments