The account to use, falls back to the default one.
The account needs a service_api_key attribute.

Table 28. Pagerduty Event Trigger Incident Attributes

Name

Required

Description

description

yes

A quick description for this event

event_type

no

The event type to sent. Must be one of trigger,
resolve or acknowledge. Defaults to trigger.

incident_key

no

The incident key on the pagerduty side, also used
for de-duplication and allows to resolve or acknowledge
incidents.

client

no

Name of the client triggering the incident, i.e.
Watcher Monitoring

client_url

no

A client URL to visit to get more detailed information.

attach_payload

no

If set to true the payload is attached as a detail
to the API call. Defaults to false.

contexts

no

An array of objects, that allow you to provide
additional links or images in order to provide more
context to the trigger.

proxy.host

no

The proxy host to use (only in combination with proxy.port)

proxy.port

no

The proxy port to use (only in combination with proxy.host)

You can configure defaults for the above values for the whole service using the
xpack.notification.pagerduty.event_defaults.* properties as well as
per account using xpack.notification.pagerduty.account.your_account_name.event_defaults.*

All of those objects have templating support, so you can use data from the
context and the payload as part of all the fields.

Table 29. Pagerduty Event Trigger Context Attributes

Name

Required

Description

type

yes

One of link or image.

href

yes/no

A link to include more information. Must be there if the
type is link, optional if the type is image