-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/master' into np-update-remaini…
…ng-client-dependencies
- Loading branch information
Showing
104 changed files
with
2,588 additions
and
1,432 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| [role="xpack"] | ||
| [[email-action-type]] | ||
| == Email action type | ||
|
|
||
| The email action type uses the SMTP protocol to send mail message, using an integration of https://nodemailer.com/[Nodemailer]. Email message text is sent as both plain text and html text. | ||
|
|
||
| [float] | ||
| [[email-connector-configuration]] | ||
| ==== Connector configuration | ||
|
|
||
| Email connectors have the following configuration properties: | ||
|
|
||
| Name:: The name of the connector. The name is used to identify a connector in the management UI connector listing, or in the connector list when configuring an action. | ||
| Sender:: The from address for all emails sent with this connector, specified in `user@host-name` format. | ||
| Host:: Host name of the service provider. If you are using the <<action-settings, `xpack.actions.whitelistedHosts`>> setting, make sure this hostname is whitelisted. | ||
| Port:: The port to connect to on the service provider. | ||
| Secure:: If true the connection will use TLS when connecting to the service provider. See https://nodemailer.com/smtp/#tls-options[nodemailer TLS documentation] for more information. | ||
| Username:: username for 'login' type authentication. | ||
| Password:: password for 'login' type authentication. | ||
|
|
||
| [float] | ||
| [[email-action-configuration]] | ||
| ==== Action configuration | ||
|
|
||
| Email actions have the following configuration properties: | ||
|
|
||
| To, CC, BCC:: Each is a list of addresses. Addresses can be specified in `user@host-name` format, or in `name <user@host-name>` format. One of To, CC, or BCC must contain an entry. | ||
| Subject:: The subject line of the email. | ||
| Message:: The message text of the email. Markdown format is supported. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| [role="xpack"] | ||
| [[index-action-type]] | ||
| == Index action type | ||
|
|
||
| The index action type will index a document into {es}. | ||
|
|
||
| [float] | ||
| [[index-connector-configuration]] | ||
| ==== Connector configuration | ||
|
|
||
| Index connectors have the following configuration properties: | ||
|
|
||
| Name:: The name of the connector. The name is used to identify a connector in the management UI connector listing, or in the connector list when configuring an action. | ||
| Index:: The {es} index to be written to. | ||
| Refresh:: Setting for the {ref}/docs-refresh.html[refresh] policy for the write request. | ||
| Execution time field:: This field will be automatically set to the time the alert condition was detected. | ||
|
|
||
| [float] | ||
| [[index-action-configuration]] | ||
| ==== Action configuration | ||
|
|
||
| Index actions have the following properties: | ||
|
|
||
| Document:: The document to index in json format. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| [role="xpack"] | ||
| [[pagerduty-action-type]] | ||
| == PagerDuty action type | ||
|
|
||
| The PagerDuty action type uses the https://v2.developer.pagerduty.com/docs/events-api-v2[v2 Events API] to trigger, acknowledge, and resolve PagerDuty alerts. | ||
|
|
||
| [float] | ||
| [[pagerduty-connector-configuration]] | ||
| ==== Connector configuration | ||
|
|
||
| PagerDuty connectors have the following configuration properties: | ||
|
|
||
| Name:: The name of the connector. The name is used to identify a connector in the management UI connector listing, or in the connector list when configuring an action. | ||
| API URL:: An optional PagerDuty event URL. Defaults to `https://events.pagerduty.com/v2/enqueue`. If you are using the <<action-settings, `xpack.actions.whitelistedHosts`>> setting, make sure the hostname is whitelisted. | ||
| Routing Key:: A 32 character PagerDuty Integration Key for an integration on a service or on a global ruleset. | ||
|
|
||
| [float] | ||
| [[pagerduty-action-configuration]] | ||
| ==== Action configuration | ||
|
|
||
| PagerDuty actions have the following properties: | ||
|
|
||
| Severity:: The perceived severity of on the affected system. This can be one of `Critical`, `Error`, `Warning` or `Info`(default). | ||
| Event action:: One of `Trigger` (default), `Resolve`, or `Acknowledge`. See https://v2.developer.pagerduty.com/docs/events-api-v2#event-action[event action] for more details. | ||
| Dedup Key:: All actions sharing this key will be associated with the same PagerDuty alert. This value is used to correlate trigger and resolution. This value is *optional*, and if unset defaults to `action:<action saved object id>`. The maximum length is *255* characters. See https://v2.developer.pagerduty.com/docs/events-api-v2#alert-de-duplication[alert deduplication] for details. | ||
| Timestamp:: An *optional* https://v2.developer.pagerduty.com/v2/docs/types#datetime[ISO-8601 format date-time], indicating the time the event was detected or generated. | ||
| Component:: An *optional* value indicating the component of the source machine that is responsible for the event, for example `mysql` or `eth0`. | ||
| Group:: An *optional* value indicating the logical grouping of components of a service, for example `app-stack`. | ||
| Source:: An *optional* value indicating the affected system, preferably a hostname or fully qualified domain name. Defaults to the {kib} saved object id of the action. | ||
| Summary:: An *optional* text summary of the event, defaults to `No summary provided`. The maximum length is 1024 characters. | ||
| Class:: An *optional* value indicating the class/type of the event, for example `ping failure` or `cpu load`. | ||
|
|
||
| For more details on these properties, see https://v2.developer.pagerduty.com/v2/docs/send-an-event-events-api-v2[PagerDuty v2 event parameters]. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| [role="xpack"] | ||
| [[server-log-action-type]] | ||
| == Server log action type | ||
|
|
||
| This action type writes and entry to the {kib} server log. | ||
|
|
||
| [float] | ||
| [[server-log-connector-configuration]] | ||
| ==== Connector configuration | ||
|
|
||
| Server log connectors have the following configuration properties: | ||
|
|
||
| Name:: The name of the connector. The name is used to identify a connector in the management UI connector listing, or in the connector list when configuring an action. | ||
|
|
||
| [float] | ||
| [[server-log-action-configuration]] | ||
| ==== Action configuration | ||
|
|
||
| Server log actions have the following properties: | ||
|
|
||
| Message:: The message to log. |
Oops, something went wrong.