Enhanced Notification Reporting and Filtering Capabilities
As an IT Operations Manager,
I want to generate reports on triggered notifications with customizable date/time filters and view aggregated notification metrics,
so that I can efficiently analyze notification trends, create weekly performance reports for stakeholders, and identify patterns in system alerts without manually scanning through individual log entries.
We report weekly on the number of notifications / escalations of notifications we get. Currently there is no way to run a report on notification templates or notification templates > objects. Allow users to run reports on the objects within the notification templates or allow users to filter better in the logs>system events>notifications - as it currently only allows you to filter per date/time. This is still making a user filter per date/time then scanning through every notification to be able to report for the week.
Best option:
One report allowing to show total number of triggered notifications per date/time filter
Second choice:
Add a filter to logs>systems events>notifications - to allow for filtering notifications that were triggered
Cathy Shehorn
shared this idea
Hi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time, as we unfortunately won't be able to prioritize treating notifications and notification templates as monitored objects in our current roadmap. However, we'd like to suggest a few alternatives that may help in the meantime:
- System Logs + CSV Export: Navigate to Logs in the main menu, filter by System Events for notification activity, and use the Export to CSV option at the bottom to build custom reports in Excel.
- Write-to-File Notification: Create a notification using the Execute Program action, pointing to a simple script that appends placeholders (%sensor, %status, %datetime) to a .csv file. This gives you a permanent, searchable audit trail outside of PRTG's log rotation.
- PRTG API / PrtgAPI (PowerShell): Query notification logs programmatically. With the community-supported PrtgAPI (see Home · lordmilko/PrtgAPI Wiki · GitHub), a command like Get-PrtgLog -StartDate (Get-Date).AddDays(-7) | Where-Object { $_.Status -eq "NotificationSent" } lets you pipe results directly into a CSV or HTML report.
- External Syslog / SIEM Integration: For long-term compliance reporting, configure a notification to send Syslog messages (Setup > Account Settings > Notifications > Send Syslog Message) to an external tool like Graylog or a SIEM, enabling advanced historical reporting without impacting PRTG performance.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team