Hi everybody
in a report, the availabilty of a sensor is summarized, that works well. But sometimes, I do not want all the errors or unknown stats to run into it:
- a device was down for maintenance and it was forgotten to pause its sensors before - PRTG itself got a ugrade or reboot - the route to a host was lost, but the host itself was online
Is there a way to mark errors as non-errors?
Kind regards, Torsten
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Thank you Torsten, but that does not please me.
Handling all the data seems very complex and takes a lot of time. Is there a way to gather only the faults?
May, 2014 - Permalink
For errors that already occurred, you could use the PRTG API again, to get the messages of a sensor per API-Call. But this would be on a 1-by-1 sensor basis again.
For future errors, you could look into adapting a solution similar to the one in the following KB-Articel: https://kb.paessler.com/en/topic/20553-report-of-all-alerts-received
May, 2014 - Permalink
Hello,
thank you very much for your KB-Post. I'm very much afraid it's not yet possible to 'flag' certain sensor states in a report. We do have this on our wishlist. In the moment, I can only suggest to gather the historic data via the PRTG API (Setup->PRTG API->Historic Data), and then "generate" the report externally (of PRTG). This would allow you to flag / mark down times, etc..
best regards.
May, 2014 - Permalink