AsyncAPI channel · Sumo Logic · Sumo Logic Webhook Connections

pagerduty

PagerDuty Events API V2. Sumo Logic POSTs to `https://events.pagerduty.com/v2/enqueue` with a routing key, event action (`trigger` or `resolve`), client metadata, and a `payload` object describing the incident. Per Sumo Logic guidance, the `routing_key`, `event_action`, and `dedup_key` fields must not be altered in the payload template.

Open source AsyncAPI → All Sumo Logic channels Sumo Logic provider profile
Provider: Sumo Logic AsyncAPI: v2.6.0 Spec: Sumo Logic Webhook Connections Operations: 1 Messages: 2

Channel address

pagerduty

Operations

publish
postPagerDutyEvent
Deliver a Sumo Logic alert as a PagerDuty Events API V2 event.

Messages

PagerDutyTriggerEvent
PagerDuty Events API V2 trigger event
Content-Type: application/json
PagerDutyResolveEvent
PagerDuty Events API V2 resolve event
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.