Navigate to Services > Service Details > Alert Grouping (or configure via the Services API with alert_grouping_parameters in the service payload)
Choose Time-Based grouping to collapse all alerts on the service into the open incident for a fixed window (1–60 minutes); set time_window to desired seconds in the API payload
Choose Content-Based grouping to group only alerts where selected fields match exactly; specify fields as a list of dot-path strings in the fields array of alert_grouping_parameters
Choose Intelligent Alert Grouping (machine-learning based) by setting type to intelligent; optionally set time_window for the ML correlation window
Enable Unified Alert Grouping (combines Content-Based and Intelligent) by setting type to unified with both content fields and an intelligent time window — alerts group only when both conditions are met
Validate grouping behavior using PagerDuty's 'Preview Intelligent Alert Grouping' feature on the service page before enabling in production
Known gotchas
Intelligent and Unified Alert Grouping are premium features; confirm your PagerDuty plan includes them before configuring — the API returns a 402 or validation error if the plan does not support them
Content-Based grouping requires exact field matches — partial matches or missing fields will prevent grouping; test with representative alert payloads before relying on it in production
Alert grouping is configured per-service; global deduplication (matching on dedup_key) is separate and applies before grouping — ensure dedup_keys are set consistently in events sent via Events API v2
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp