2 results found

1. Allow securely passing PRTG HTTP API credentials in Notification Template "Execute HTTP Action" section

   As a Systems Engineer managing a mixed environment of always-on and intermittently connected devices, I want to use the "Parameters" field "Execute HTTP Action" section of Notification Templates with secure placeholders so that we can make a PRTG HTTP API call without having to put credentials in clear text.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Operational Notices — Time-Bound Annotations Without Alert Suppression

   As a Systems Engineer performing planned operational work (patching, failover testing, load testing),
   I want to attach a time-bound, human-readable notice to a device, group, or the entire PRTG environment
   so that alerts continue to fire for validation purposes while my colleagues (NOC staff, on-call engineers, managers) can immediately see that those alerts are expected — without relying on external communication or fragile workarounds.

   In operational environments there are regular situations where engineers intentionally generate alerts during testing, validation, or controlled changes (e.g. patching, failover testing, load testing).

   In these cases:
   - Alerts must continue to fire so the engineer performing the work can validate behaviour.
   - Other users (on-call, NOC, managers) need clear visibility that these alerts are expected.

   Currently, PRTG tightly couples alert context to monitoring state:
   - Pausing sensors or maintenance windows suppress alerts, which breaks testing.
   - Acknowledgements are reactive and per-alert.
   - Channel messages and tags are static and not time-bound.
   - There is no dedicated place to add human context that is visible alongside alerts.

   As a result, teams rely on workarounds (Maps text, dummy sensors, external communications), which are easy to miss and inconsistent.

   Feature request:
   Introduce an operational notice / annotation feature that allows authorised users to post a time-bound, human-readable message that is visible in the PRTG UI without affecting monitoring or alerting.

   Key characteristics:
   - Does not suppress alerts or change sensor state
   - Can be scoped (global, group, or device level)
   - Supports free-text messages (e.g. “Expected alerts during patching until 22:00”)
   - Optional start and end time
   - Visible in relevant views (alarms list, object tree, dashboards)
   - Auditable (who set it and when)

   This would preserve alert accuracy while improving shared operational awareness and reducing alert fatigue.

   As a Systems Engineer performing planned operational work (patching, failover testing, load testing),
   I want to attach a time-bound, human-readable notice to a device, group, or the entire PRTG environment
   so that alerts continue to fire for validation purposes while my colleagues (NOC staff, on-call engineers, managers) can immediately see that those alerts are expected — without relying on external communication or fragile workarounds.

   In operational environments there are regular situations where engineers intentionally generate alerts during testing, validation, or controlled changes (e.g. patching, failover testing, load testing).

   In these cases:
   - Alerts must continue to fire so the engineer… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating