pagerduty.EventOrchestrationGlobal

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

the catch_all actions will be applied if an Event reaches the end of any set without matching any rules in that set.

ID of the Event Orchestration to which this Global Orchestration belongs to.

A Global Orchestration must contain at least a "start" set, but can contain any number of additional sets that are routed to by other rules to form a directional graph.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

These are the actions that will be taken to change the resulting alert and incident. catch_all supports all actions described above for rule except route_to action.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Actions that will be taken to change the resulting alert and incident, when an event matches this rule.

Each of these conditions is evaluated to check if an event matches this rule. The rule is considered a match if any of these conditions match. If none are provided, the event will always match against the rule.

Indicates whether the rule is disabled and would therefore not be evaluated.

The ID of this set of rules. Rules in other sets can route events into this set using the rule's route_to property.

A description of this rule's purpose.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Add this text as a note on the resulting incident.

Create a Webhook associated with the resulting incident.

When true, this event will be dropped. Dropped events will not trigger or resolve an alert or an incident. Dropped events will not be evaluated against router rules.

sets whether the resulting alert status is trigger or resolve. Allowed values are: trigger, resolve

Replace any CEF field or Custom Details object field using custom variables.

The ID of the priority you want to set on resulting incident. Consider using the pagerduty.getPriority data source.

The ID of a Set from this Global Orchestration whose rules you also want to use with events that match this rule.

sets Severity of the resulting alert. Allowed values are: info, error, warning, critical

Set whether the resulting alert is suppressed. Suppressed alerts will not trigger an incident.

The number of seconds to suspend the resulting alert before triggering. This effectively pauses incident notifications. If a resolve event arrives before the alert triggers then PagerDuty won't create an incident for this alert.

Populate variables from event payloads and use those variables in other event actions.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name of this Webhook.

The API endpoint where PagerDuty's servers will send the webhook request.

When true, PagerDuty's servers will automatically send this webhook request as soon as the resulting incident is created. When false, your incident responder will be able to manually trigger the Webhook via the PagerDuty website and mobile app.

Specify custom key/value pairs that'll be sent with the webhook request as request headers.

Specify custom key/value pairs that'll be included in the webhook request's JSON payload.

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

Name to identify the header

Value of this header

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

The PagerDuty Common Event Format PD-CEF field that will be set with the value from the template or based on regex and source fields.

A RE2 regular expression that will be matched against field specified via the source argument. If the regex contains one or more capture groups, their values will be extracted and appended together. If it contains no capture groups, the whole match is used. This field can be ignored for template based extractions.

The path to the event field where the regex will be applied to extract a value. You can use any valid PCL path like event.summary and you can reference previously-defined variables using a path like variables.hostname. This field can be ignored for template based extractions.

A string that will be used to populate the target field. You can reference variables or event data within your template using double curly braces. For example:

• Use variables named ip and subnet with a template like: {{variables.ip}}/{{variables.subnet}}
• Combine the event severity & summary with template like: {{event.severity}}:{{event.summary}}

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

Name of this Webhook.

Path to a field in an event, in dot-notation. This supports both PagerDuty Common Event Format PD-CEF and non-CEF fields. Eg: Use event.summary for the summary CEF field. Use raw_event.fieldname to read from the original event fieldname data. You can use any valid PCL path.

Only regex is supported

Value of this header

A PCL condition string.

A PCL condition string.

A PCL condition string.

A PCL condition string.

A PCL condition string.

A PCL condition string.