What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Miss leading downtime reporting



Your Vote:



Hi All,

We are using PRTG now for a while and it looks great. Although I have a question about the downtime reporting and the workflow for that.

When an sensor is in ERROR, we acknowledge that error and I will investigate. When I cannot solve the problem, I inform a collegeau and he will fix it. This can take a while (< 1hr). In the meantime, the ERROR is acknowledged but I still see PRTG is trying to get statistics of that sensor. My downtime reporting of that sensor is very low because of that workflow.

What is your suggesting to handle this kind of things?

Also I want to have a print-out of all the tickets and there information as a report. Is that possible?

Best regards

downtime reporting workflow

Created on Jan 20, 2015 1:41:55 PM by  Poort80 Hosting Services (0) 1

1 Reply



Your Vote:




your procedure to acknowledge down sensors is correct.

As an alternative, you can Pause the sensor to decrease the downtime.

I´m afraid to get ticket information into a report it not possible. I'll put in onto the "wishlist" stack, and see what we can do about it.

Created on Jan 22, 2015 4:54:17 PM by  Jochen Greger [Paessler Support]

Please log in or register to enter your reply.

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.