* Legacy Documentation for Statseeker v5.5.5 *

Index


Overview

By default, Statseeker communicates with monitored hardware via Internet Control Method Protocol (ICMP) to determine device availability. Each monitored device on your network receives a ping request from your Statseeker server every 15 seconds. These requests are staggered over time and target devices spread across the network to ensure that this activity doesn’t overly target any single subnet at any time.

Ping polling is enabled for all monitored devices by default, but operates independently from other polling methods within Statseeker, and can be enabled/disabled for each monitored device. Devices can also be added to Statseeker as ‘ping-only’ devices, where they are monitored for availability but not monitored via SNMP. For more information see Adding Ping-Only Devices.

Statseeker collects a range of ping related data:

Timeseries and Event Data

  • Ping Duplicate – number of duplicate ping responses received
  • Ping Lost 1 – number of times that a single ping request is lost
  • Ping Lost 2 – number of times that two ping requests in a row have been lost
  • Ping Lost 3 – number of times that three ping requests in a row have been lost
  • Ping Lost 4 – number of times that four (or more) ping requests in a row have been lost
  • Ping RTT – current ping return trip time in milliseconds
  • Ping RTT(High Precision) – Ping RTT to 3 decimal places
  • Ping State – current ping state of the device (up/down)

Configuration Data

  • Ping Outage – the number of seconds which must elapse after a Ping Lost is recorded before a device is declared ‘down’ (default 45s)
  • Ping Poll – the device’s ping polling status (on/off)

[top]

Ping Lost Counters

The Ping Lost counters are updated at the time of the next successful ping response and the update reflects the highest Ping Lost value seen since the previous successful ping – if 3 pings are lost, only the Ping Lost 3 is recorded, Ping Lost 1/2 are not updated as it was a Ping Lost 3 event.

Ping Lost data is collected every 15 seconds (with each ping request) and this data is then bundled and inserted into the database on an hourly schedule. Other ping related data is not subject to this bundling process and is inserted at collection.

Example:

  • Ping sent and no response received – Ping Lost 1 recorded
  • 15s later, ping sent and no response received – Ping Lost 2 recorded
  • 15s later, ping sent and no response received – Ping Lost 3 recorded
  • 15s later, ping sent and response received – Ping Lost 3 counter updated



[top]

Ping Outage and State

The Ping State for a monitored device is updated as a result of the ping response, or lack there of, returned by the device. Each device has an associated Ping Outage value (defaults to 45s) which specifies the number of seconds to wait after a Ping Lost event before a device is declared ‘down’.

Example:

  • Ping sent and no response received – Ping Lost 1 recorded
  • 15s later, ping sent and no response received – Ping Lost 2 recorded
  • 15s later, ping sent and no response received – Ping Lost 3 recorded
  • 15s later, ping sent and no response received – Ping Lost 4 recorded and device declared ‘down’
  • 15s later, ping sent and no response received – Ping Lost 4 recorded
  • 15s later, ping sent and response received – Ping Lost 4 counter updated and device declared ‘up’


A device’s Ping Outage value can be adjusted enabling you to tailor the time Statseeker waits, prior to declaring the device ‘down’, to suit that specific device and its location within your network. Please contact Statseeker Support to discuss this requirement.

[top]