Report for Ping 269
Report Time Span: 4/10/2012 12:00:00 AM - 4/10/2012 11:59:00 PM
Sensor Type: Ping (30 s Interval)
Probe, Group, Device: Local probe > Internet Sites > Basemine Maintenance BT 2
Uptime Stats:Up: 95.64 % [22h55m46s] Down: 4.36 % [1h2m43s]
Request Stats:Good: 94 % [2705] Failed: 6 % [177]
Average (Ping Time): 594 msec
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.
Hello,
uptime means the uptime of course. For requests it's slightly different, because PRTG only accounts downtime between at least two consecutive failed scans. So if only one request fails, it's accounted as failed/bad request but does not effect uptime. If a scan fails, the sensor goes down. To be exact, with most sensors after a failed scan PRTG performs an immediate re-scan and if these both fail, the sensor goes into down state. But that gives no exact measurement for downtime, PRTG can't know how long the target is already down. So it takes at least one more scan following the scanning interval for PRTG to have a proper valid statement for downtime.
best regards.
Apr, 2012 - Permalink
Hello,
uptime means the uptime of course. For requests it's slightly different, because PRTG only accounts downtime between at least two consecutive failed scans. So if only one request fails, it's accounted as failed/bad request but does not effect uptime. If a scan fails, the sensor goes down. To be exact, with most sensors after a failed scan PRTG performs an immediate re-scan and if these both fail, the sensor goes into down state. But that gives no exact measurement for downtime, PRTG can't know how long the target is already down. So it takes at least one more scan following the scanning interval for PRTG to have a proper valid statement for downtime.
best regards.
Apr, 2012 - Permalink