14 results found
-
Differentiate the Sensor Down State from Error State
As a Systems Engineer, I want PRTG to distinguish between Down status (when monitored services fail operational thresholds) and Error status (when sensors cannot capture data due to communication/protocol issues) so that I can configure separate notifications to alert operations teams about actual service failures while directing data acquisition problems to monitoring administrators.
15 votes -
Mute alerts during maintenance
As an IT Administrator I would like to mute alarms during a maintenance window without pausing sensors so that I can ensure I am collecting as much data is possible without creating false positives.
This is a feature which other tools have
21 votes -
Persist Acknowledged Sensor Status After Server Restart
As a Systems Engineer,
I want acknowledged sensor alarms to remain in the "Down (Acknowledged)" status after a PRTG server restart,
so that I don't receive duplicate notifications for issues I've already acknowledged and can maintain consistent alarm management across server maintenance windows.5 votesHi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
-
Enhanced State Triggers for Acknowledged and Paused Sensor States
As an IT Operations Manager, I want configurable notification triggers for sensors in "Down (Acknowledged)" and "Paused" states so that I can maintain complete operational visibility and ensure downstream systems and teams are informed about all sensor state changes, even when issues are being managed.
Currently, state trigger has the options "When sensor state is Down/ Warning/ Unusual/ Down (Partial)/ Up/ Unknown...", but we need additional status trigger when a sensor enters "Paused" or "Down (acknowledged)" status. E.g. the systems following in the alarming process might need to know, the issue is still current (but acknowledged).
6 votes -
Add Monthly Recurring Maintenance Schedule Option
As a PRTG user, I want to create monthly recurring maintenance schedules for devices with scheduled reboots so that I can enable 24/7 push notifications without being woken up by false alarms during planned maintenance activities.
13 votes -
SYSLOG Receiver - Single Message Variables for Enhanced Email Subject Line Notifications
As a Systems Engineer or Network Engineer, I want single-message placeholder variables (%sysloglasterror, %sysloglastwarning) that work in email subject lines so that I can immediately identify critical syslog issues from my inbox or mobile device without opening emails, enabling faster incident response and problem resolution.
5 votes -
Enhanced HTTP Action Notifications: JSON/XML Support with Custom Headers
As an IT Operations Engineer, I want to send PRTG notifications in JSON or XML format with custom HTTP headers so that I can directly integrate PRTG alerts with modern ITSM, incident management, and automation systems, eliminating manual steps and custom scripting.
11 votes -
Disable Unknow State
Hello,
As a cybersecurity engineer, I want to avoid unknown states.
We manage a large number of devices across many different sites, and sometimes we lose SNMP data for a specific sensor. When this happens while the sensor is actually in a down state, the status transitions follow this pattern:
Down → Unknown → Down.
This generates a lot of phantom notifications, and even worse, our acknowledged alerts revert to an unacknowledged state.
Could you please add an option to ignore or bypass the unknown state in such cases?
Thank you.
Best regards.1 vote -
BCC Field for Email Notifications
As an IT Operations Manager, I want to configure BCC recipients in PRTG email notifications so that I can send alerts to external systems and tracking mailboxes without exposing those addresses to other notification recipients, ensuring security and regulatory compliance.
Use case: we need to integrate PRTG with Jira using email BCC (not API). Jira’s email address must remain hidden from other recipients for security and compliance. Additionally, a copy of each alert must be sent silently to a tracking mailbox.
The goal is to send alerts to Jira via email (address hidden from users) and to archive notifications for…
3 votes -
Complete Group Hierarchy Path Placeholder for Email Notifications
As an IT Infrastructure Manager managing a complex multi-site environment, I want email notifications to display the complete group hierarchy path so that I can immediately understand the exact location and business context of alerts without requiring additional system lookups.
Desired Outcome/Acceptance Criteria
Users should be able to use a new placeholder (e.g., %devicefullpath or %grouppath) in email notification templates
The placeholder should resolve to display the complete group hierarchy path from probe to device
Format should be: ProbeName > Group Level 1 > Group Level 2 > ... > Group Level N > DeviceName (IP)
The feature should work…4 votes -
Advanced Cron-Style Scheduling for Maintenance Windows
As an IT Infrastructure Manager, I want to define maintenance windows using Unix cron syntax so that I can schedule complex recurring maintenance patterns (like "first Saturday of each month" or "last Sunday") without manually creating individual maintenance windows each time.
Note : This would be something we would deliver with the new notification system which is not yet on the roadmap
3 votes -
Get Notified and Track Discovery Changes
As a PRTG user, I want to be notified when a discovery job finishes and have a clear history of what was added, changed, or removed so I can act quickly and keep track of changes.
3 votes -
System Information Variables for Notifications
As a Network Administrator, I want system information discovered by PRTG (such as system contact, location, description, and hardware details) to be available as variables in notification templates so that I can include relevant system context in alerts without manually maintaining duplicate information, enabling faster incident response and more informative notifications.
6 votes -
SLA Reporter: Get notified based on SLA status
As a user who works with SLAs I want to get notified if my SLA has been breached.
2 votes
- Don't see your idea?