Target maintenance windows by check name or ID, not only tags

Maintenance windows today can only be scoped by tag (tags[], silenceAlertsTags[]) or by the account-wide pauseAllChecks / silenceAllAlerts flags. There’s no way to pause or silence a single check without either tagging it uniquely or pausing everything that shares its tag.

The ask

Allow maintenance windows to target specific checks directly by:

• checkIds[] (one or more check IDs)

• checkGroupIds[] (one or more group IDs)

• or a check name match (exact or pattern)

Available on both the UI and the POST /v1/maintenance-windows API, with the same split for silencing-only (silenceAlertsCheckIds[], etc.).

Why it matters

Enterprise customers running change management (ITSM) raise change requests that carry the specific monitor name affected by a change. Their alert-suppression automation needs to pause just that one monitor during the change window. Today the only way to do that is to tag every check uniquely, which:

• Requires rewiring the change-management to monitoring pipeline across multiple teams.

• Breaks the existing tag model, where tags represent app or service groupings (app code, system code, etc.) and are deliberately coarse.

• Forces customers to choose between pausing one monitor they care about or an entire application’s worth of monitors sharing its tag.

For customers whose automation already knows the check by name, passing that name straight through to a maintenance window is the natural fit.