[Actions] There's no way to attach additional info to the PagerDuty incident

[gmmorris]

There is no way to include extra information links to documentation for troubleshooting the down service or links to other places like our Inventory in the Pager Duty Action.

Identified as part of Infra's POC.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[pmuellr]

For reference, the params we currently support for the PagerDuty action are here:

kibana/x-pack/plugins/actions/server/builtin_action_types/pagerduty.ts

Lines 68 to 79 in 34238e5

	const ParamsSchema = schema.object(
	{
	eventAction: schema.maybe(EventActionSchema),
	dedupKey: schema.maybe(schema.string({ maxLength: 255 })),
	summary: schema.maybe(schema.string({ maxLength: 1024 })),
	source: schema.maybe(schema.string()),
	severity: schema.maybe(PayloadSeveritySchema),
	timestamp: schema.maybe(schema.string()),
	component: schema.maybe(schema.string()),
	group: schema.maybe(schema.string()),
	class: schema.maybe(schema.string()),
	},

The full list of params that can be used with the PagerDuty events v2 API is here: https://developer.pagerduty.com/docs/events-api-v2/trigger-events/

Looks like we're missing payload.custom_details, images, and links.

Images will be hard - there's at least one other issue up regarding these (I think with an investigation into how it would work with Slack).

Links will be nice once we can construct a link back to the alert in Kibana (again, separate issue open for that), and we can then just provide that link "for free".

custom_details sounds like it's going to be one of these problematic params since it's presumably an object type, and we can't "partially" update these, need to do a full update (like webhook headers). Alternatively, we could store these internally as nested array of {key: string, value: string} to avoid the partial update issue.

[govindrai]

Any updates on this? Right now the integration becomes pretty barebones because you have to manually link back to kibana and you can't send any real detail as you're limited to 1024 characters. Plus the summary field becomes the title field which makes every alert appear super verbose since we have to stuff everything into that field.

[ymao1]

cc @shanisagiv1

[cnasikas]

PR #170459 added support for links and custom_details in the connector's PagerDuty API. Issue for the UI: #170048.