Granular Control for Maintenance Windows: "Full Pause" vs. "Trigger-Only Pause" (Suppress Notifications, Keep Polling)
As a Systems Engineer, I want the option to pause only notifications/triggers during a maintenance window while sensors continue polling and recording data, so that I have full data continuity during maintenance windows while completely preventing alarm fatigue for the operations team.
Description:
Currently, pausing an object halts all sensor checks completely. In many enterprise scenarios, engineers still want PRTG to gather performance data and display status checks during maintenance, but suppress active alerting/notifications.
Default Behavior: Full Object Pause (Standard behavior: stops polling and data collection).
New Option (Checkbox): "Pause Notifications / Triggers Only"
When checked, sensors continue polling, updating status, and recording performance data.
All associated Notification Triggers (state, threshold, speed triggers) attached to the object/group/probe are suppressed for the duration of the downtime.
Benefit: Full data continuity during maintenance windows while completely preventing alarm fatigue for operations teams.
This provides modern, flexible maintenance management without compromising metric collection.