With multiple people administering our PRTG 8 install we've come to realize a strong need for some type of report that can show all configured notifications and thresholds on a sensor level. A basic list of all reasons someone may get a text message for instance.

With over 400 sensors, it's impossible to do this individually and ensure all sensors are configured appropriately.

Is there a way to get a list like this?


Article Comments

Hello,

I'm afraid such a 'report' is not really available. You could try using the "Used By"-Button on the notifications, maybe this helps a bit.

Best Regards.


Nov, 2010 - Permalink

That could be a help under certain circumstances, but it still requires we dig down into each sensor for latency and threshold information etc...

With such an active development, would this be considered for a future update? It seems this could be a fairly easy to create 'report'. I would even be happy with a notification setting export of some sort.

This could be a point of contention on expanded use by our company and really want to come up with a solution.


Nov, 2010 - Permalink

Dear Jason,

there might actually be another way, under "Sensors"->"Cross Reference", you can get/"produce" a sensor list which will also show the notifications on sensors. Maybe this is better?

Best Regards.


Nov, 2010 - Permalink

This is closer, yes. It would be perfect if instead of saying 'inherited' or '# threshold' it listed the actual notifications. Thank you for looking into this further. These two options will have to do for the time being.


Nov, 2010 - Permalink

Is there anyway to do this now that 4 years have passed?


Oct, 2014 - Permalink

Due to the very low requests on this, it was not implemented so far. I did count your post as a vote though. Please bear with us.


Oct, 2014 - Permalink

+1 View the actual Notifications / Thresholds instead of inherited / # threshold


Jun, 2015 - Permalink

+1

We would also appreciate a possibility to get a list as discribed by Jason Daemon in his primary post (which gives more information than the list shown via "Sensors"->"Cross Reference").

Is it possible to achieve this with the help of the API? I found the parameter "columns=notifiesx", but I think it gives the same data as the cross reference list. I tried the following:

https://<prtg-server>/api/table.xml?content=sensors&id=<123>&columns=notifiesx

Did I miss something?

Kind regards


Nov, 2015 - Permalink

Here's a nice tool to retrieve the current channel limits:
http://prtgtoolsfamily.com/us/products/tools/channellimits


However, it doesn't show the notification correlation.


Nov, 2015 - Permalink

What do you want exactly to change? would you please specify your request, we can build a custom script to do what you want?


Feb, 2016 - Permalink

+1 for this. It would be really useful to see at a glance all enabled notifications.


Sep, 2016 - Permalink

A lot of time have passed but for me the original request from this thread is still actual.

I was able to generate PS script to pull from API following list of attributes: Group;Device;DeviceID;Sensor;SensorID;Channel;ChannelID;LowerWarningLimit;LowerErrorLimit;UpperWarningLimit;UpperErrorLimit and what I still miss is Notification ID, NotificationType,NotificationName,NotificationDelay,NotificationClear - or at least any subset of these.

The business target for these is as it was already written before - for dozen of active users there should be a way to have a helicopter view of what was configured in the Notifications area and to spot irregularities and missing notifications for devices of sensors.


Jun, 2018 - Permalink

The way we store this information doesn't make it easy to read it, I admit. Could you provide your script so I can extend it accordingly to have what you require (well, at least that what I'm able to add)?


Kind regards,
Stephan Linke, Tech Support Team


Jun, 2018 - Permalink

This would be of use to me as well, having something that you can load into excel so you can filter etc to check that the same sensor on multiple devices are all configured the same. and maybe an indicator if the sensor property shown is inherited or local to that sensor.


Jun, 2018 - Permalink