we made alot of notifications on alot of sensors on different servers.
is there a way to create a list of the notifications and there setting of those specific servers?
for example
server nt296
cpu load - notificationtrigger: when sensor state is down for at least 600 sec perform <mailto> when sensor state is down for at least 300 sec perform no notification and repeat every 0 min when condition clears afters a notification perform <mailto>
server nt297
cpu load - notificationtrigger: when sensor state is down for at least 900 sec perform <mailto> when sensor state is down for at least 600 sec perform no notification and repeat every 0 min when condition clears afters a notification perform <mailto>
This listing enables us to check if the notifications are correct and we could verify those settings to other servers to see if there are the same.
Best regards,
John Nijssen
Article Comments
"Via Setup | Account Settings | Notifications, you can use the "Used By ..." button to see which objects use that particular notification, but you cannot review the actual trigger settings for those objects." I can remember I was using this in the past but "Used By" button seems to be lost in one of the recent upgrades - dear support, could you check this please?
Jun, 2018 - Permalink
Dear Tomasz,
the "used by" feature is available once you marked a notification. Marking opens a context-menu on the right-hand side, which has an icon for "used by".
Jun, 2018 - Permalink
Dear nijssen
I am sorry, this is not directly possible. While some sensor properties are accessible via the PRTG API, the notification is stored in subnodes which cannot be access via the API.
Via Setup | Account Settings | Notifications, you can use the "Used By ..." button to see which objects use that particular notification, but you cannot review the actual trigger settings for those objects.
If you absolutely need an overview of this kind, please create a copy of the "PRTG Configuration.dat", found in "C:\ProgramData\Paessler\PRTG Network Monitor". Open the copy of the aforementioned file, which is an XML. With parsing the right nodes, you can read the trigger settings for each object.
Jan, 2016 - Permalink