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: docs/data-sources/alert.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ subcategory: "Notifications"
5
5
description: |-
6
6
Alerts let you monitor data including network traffic and activities, or various security events like password resets and missing certificates.
7
7
You can examine and filter any type of event, as well as define alert notifications to be sent to email, webhooks (integrating with SaaS apps), PagerDuty or Slack.
8
-
Alerts can configure either spike_condition or threshold_condition
8
+
Alerts can be configured using either spike_condition or threshold_condition
9
9
---
10
10
11
11
# pfptmeta_alert (Data Source)
12
12
13
13
Alerts let you monitor data including network traffic and activities, or various security events like password resets and missing certificates.
14
14
You can examine and filter any type of event, as well as define alert notifications to be sent to email, webhooks (integrating with SaaS apps), PagerDuty or Slack.
15
-
Alerts can configure either `spike_condition` or `threshold_condition`
15
+
Alerts can be configured using either `spike_condition` or `threshold_condition`
16
16
17
17
## Example Usage
18
18
@@ -44,16 +44,16 @@ output "alert" {
44
44
You can use free text and/or alert field names surrounded with a "${ }". For example, "${hits} have failed to login".
- **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for more.
48
-
- **api_audit** - The `api_audit` logs captures details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for more.
49
-
- **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for more.
50
-
- **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access from their employees into web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for more.
51
-
- **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for more
47
+
- **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for details.
48
+
- **api_audit** - The `api_audit` logs capture details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for details.
49
+
- **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for details.
50
+
- **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access of their employees to web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for details.
51
+
- **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for details
52
52
.
53
53
-**spike_condition** (List of Object) (see [below for nested schema](#nestedatt--spike_condition))
54
54
-**threshold_condition** (List of Object) (see [below for nested schema](#nestedatt--threshold_condition))
55
55
-**type** (String)
56
-
-**window** (Number) The time window of the check (in mins), ENUM: 1, 3, 5, 10, 30, 60, 360, 1440, 2880, 10080.
56
+
-**window** (Number) The time window of the check (in mins), ENUM: `1`, `3`, `5`, `10`, `30`, `60`, `360`, `1440`, `2880`, `10080`.
Copy file name to clipboardExpand all lines: docs/resources/alert.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ subcategory: "Notifications"
5
5
description: |-
6
6
Alerts let you monitor data including network traffic and activities, or various security events like password resets and missing certificates.
7
7
You can examine and filter any type of event, as well as define alert notifications to be sent to email, webhooks (integrating with SaaS apps), PagerDuty or Slack.
8
-
Alerts can configure either spike_condition or threshold_condition
8
+
Alerts can be configured using either spike_condition or threshold_condition
9
9
---
10
10
11
11
# pfptmeta_alert (Resource)
12
12
13
13
Alerts let you monitor data including network traffic and activities, or various security events like password resets and missing certificates.
14
14
You can examine and filter any type of event, as well as define alert notifications to be sent to email, webhooks (integrating with SaaS apps), PagerDuty or Slack.
15
-
Alerts can configure either `spike_condition` or `threshold_condition`
15
+
Alerts can be configured using either `spike_condition` or `threshold_condition`
- **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for more.
70
-
- **api_audit** - The `api_audit` logs captures details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for more.
71
-
- **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for more.
72
-
- **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access from their employees into web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for more.
73
-
- **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for more
69
+
- **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for details.
70
+
- **api_audit** - The `api_audit` logs capture details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for details.
71
+
- **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for details.
72
+
- **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access of their employees to web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for details.
73
+
- **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for details
74
74
.
75
-
-**window** (Number) The time window of the check (in mins), ENUM: 1, 3, 5, 10, 30, 60, 360, 1440, 2880, 10080.
75
+
-**window** (Number) The time window of the check (in mins), ENUM: `1`, `3`, `5`, `10`, `30`, `60`, `360`, `1440`, `2880`, `10080`.
Copy file name to clipboardExpand all lines: internal/provider/alert/common.go
+12-12Lines changed: 12 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -11,25 +11,25 @@ import (
11
11
const (
12
12
description="Alerts let you monitor data including network traffic and activities, or various security events like password resets and missing certificates.\n"+
13
13
"You can examine and filter any type of event, as well as define alert notifications to be sent to email, webhooks (integrating with SaaS apps), PagerDuty or Slack.\n"+
14
-
"Alerts can configure either `spike_condition` or `threshold_condition`"
14
+
"Alerts can be configured using either `spike_condition` or `threshold_condition`"
15
15
channelsDesc="List of notification channel IDs."
16
16
groupByDesc="The group by field name."
17
17
notifyMessageDesc="Creates a custom message that will be sent to your notification channels.\n"+
18
18
" You can use free text and/or alert field names surrounded with a \"${ }\". For example, \"${hits} have failed to login\"."
" - **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for more.\n"+
21
-
" - **api_audit** - The `api_audit` logs captures details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for more.\n"+
22
-
" - **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for more.\n"+
23
-
" - **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access from their employees into web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for more.\n"+
24
-
" - **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for more\n."
20
+
" - **security_audit**- The `security_audit` logs provide the administrator visibility into events which are generated by device and user security-related activity, such as user authenticating into Proofpoint NaaS, users changing their passwords, posture check failures, etc. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#security-logs) for details.\n"+
21
+
" - **api_audit** - The `api_audit` logs capture details of administrator activity: the timestamp and identity of administrators who accessed the Proofpoint NaaS tenant, and configuration changes that were made by the administrator. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#audit-logs) for details.\n"+
22
+
" - **traffic_audit** - The `traffic_audit` logs provide detailed visibility into each element in the system covering network traffic including DNS and other OSI Layer 3 and 4 traffic details. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#traffic-logs) for details.\n"+
23
+
" - **metaproxy_audit** - The `metaproxy_audit` logs provide the administrator visibility into the clientless access of their employees to web applications configured via EasyLink policy. See [here](https://help.metanetworks.com/knowledgebase/admin_console_logs/#metaconnect-web-logs) for details.\n"+
24
+
" - **webfilter_audit** - The `webfilter_audit` logs provide the administrator visibility into the events generated by the Web Security engine. See [here](https://help.metanetworks.com/knowledgebase/logs_ws/) for details\n."
25
25
minHitsDesc="Minimum number of hits in current window to check the spike."
26
-
spikeRatioDesc="The diff between hits that triggers alert (in percents)"
0 commit comments