4 results found

1. Detailed export of sensor configuration data

   I need an Excel/CSV export of all sensors including sensor type and their configured thresholds, notifications, triggers and dependend device and structure. It is very important for the regulated pharmaceutical sector to have a detailed configuration overview.

   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

   1 comment  ·  Delete…  ·  Admin →
   Declined  ·  AdminJonah Kowall (SVP Product and Design, Paessler) responded

   As David mentioned this particular issue should be handled with the new API (v2). If not please feel free to get back in touch.

2. 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

   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… 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

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   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

   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… more

3. Enable Parent Tag Filtering for MultiBoard Dashboards

   As an IT Manager,
   I want to filter sensors in MultiBoard dashboards using parent tags (from groups, devices, or probes) instead of only sensor-level tags,
   so that I can create flexible, hierarchical dashboards that automatically include all sensors under tagged organizational units without manually tagging each individual sensor.

   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

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminDaniel Elsner (Product Manager, Paessler) responded

   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. This decision was made based on several factors, which may include:

   • It doesn't align with our current product roadmap or strategic priorities.
   • The resources required for implementation outweigh the current projected benefits for our user base.
   • There are technical limitations that prevent us from moving forward.
   • A similar feature is already available or planned in a different way.

   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

4. Group & Lock Items when creating Maps

   When trying to layout items on the Map, it would be nice to have the ability to group and lock items on the map while trying to layout the design. Right now you have to individually move each item which makes it very difficult to organize the map layout.

   It would also be nice if there was an option to align the different items on the map. If I add a shape to the map and then add a sensor, it is a tedious task to try and center the sensor in that shape.

   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

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminJonah Kowall (SVP Product and Design, Paessler) responded

   Hi there,

   Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.

   Mapping is going to be replaced with new dashboarding and visualization next year, hence this request is no longer valid. If you would like to be in the beta for the new dashboarding and visualization I am happy to get you into that program when we kick it off in the middle of next year.

   After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:

   • It doesn't align with our current product roadmap or strategic priorities.
   • The resources required for implementation outweigh the current projected benefits for our user base.
   • There are technical limitations that prevent us from moving forward.
   • A similar feature is already available or planned in a different way.

   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

   Hi there,

   Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.

   Mapping is going to be replaced with new dashboarding and visualization next year, hence this request is no longer valid. If you would like to be in the beta for the new dashboarding and visualization I am happy to get you into that program when we kick it off in the middle of next year.

   After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:

   • It doesn't align with our current product roadmap or strategic priorities.
   • The resources required for implementation outweigh the current projected benefits for our user base.
   • There are technical limitations that prevent us from moving forward.
   • A similar feature is already available or planned in a different way.

   … more