alert_renotify#
Send a notification once every frequency_minutes minutes if any events come in to any issues.
Inputs#
Name |
Description |
Type |
Default |
Required |
|---|---|---|---|---|
A string to append to the name of this alert |
|
|
no |
|
Name of the environment for which to trigger the alert |
|
n/a |
yes |
|
A string determining which filters need to be true before any actions take place. Required when a value is provided for filters. Valid values are: all, any, and none. |
|
|
no |
|
A list of filters that determine if a rule fires after the necessary conditions have been met. In JSON string format. The JSON schema used to be here (search the page for ‘filters’): https://docs.sentry.io/api/monitors/create-an-alert-for-an-organization/, but now seems not to exist anwhere in Sentry’s docs :| We are using this deprecated attribute instead of filters_v2 because we can not assign the filters_v2 attribute from a variable: jianyuan/terraform-provider-sentry#551 |
|
|
no |
|
How often to perform the actions once for an issue, in minutes. The valid range is 5 to 43200. |
|
n/a |
yes |
|
Text to show alongside the notification. To @ a user, include their user id like @<USER_ID>. To include a clickable link, format the link and title like <http://example.com|Click Here>. |
|
|
no |
|
The organization (slug) in which to provision this alert |
|
n/a |
yes |
|
Trigger the alert for this project (slug) |
|
n/a |
yes |
|
Slack channel to notify when the alert goes off. Must begin with ‘#’ |
|
n/a |
yes |
|
Tags to include in the notification |
|
|
no |