Volver a la wiki

Collected metrics

What it is

Observatory collects metrics through ping (ICMP), SNMP polling and HTTP checks. Time-series data lives in a dedicated metrics engine with 180 days of retention; configuration and alerts live in the main database. This page lists what is collected, how often, and how far back you can look.

Metrics collected

Heartbeat (Ping)

MetricUnitDescription
LatencymsRound-trip time of the ICMP packet
Packet loss%Probes sent that got no reply
StatusUp / DownWhether the device answered

From these, Observatory derives average, minimum, maximum latency and uptime % for the selected period.

Bandwidth and errors (SNMP)

MetricUnitDescription
Inbound trafficMbpsData received on the monitored interface
Outbound trafficMbpsData sent on the monitored interface
AggregateMbpsIn + Out, optional line (Agg button)
Interface errorsper minuteCRC errors, malformed frames
Discardsper minutePackets dropped by the interface

Both 32-bit and 64-bit (high-capacity) SNMP counters are supported, so multi-gigabit links read correctly. You pick the monitored interface from the dropdown in the Bandwidth (SNMP) section.

Resources and environment (vendor OIDs)

On devices where Deep Discovery identified the vendor, Observatory also polls CPU usage, memory usage and temperature. These charts appear automatically once the OIDs are known — see [[crearack—monitoring—deep-discovery]].

HTTP checks

HTTP health checks record status code, response time (ms), SSL validity and days until certificate expiration. Results feed alerts rather than a dedicated chart — see [[crearack—monitoring—ping-http]].

Wireless access points and UPS devices have richer, specialized metric sets in their own modules: [[crearack—monitoring—que-es-wireless]] and [[crearack—monitoring—que-es-ups]].

How often

Every monitored device has its own Polling cadence — 15 s, 30 s, 1 min (default) or 5 min — set in its card editor; its charts refresh at the same pace. See [[crearack—network—device-page]].

ModeCheckInterval
Cloud OnlyAll enabled checksWhile the device tab is open, at the device’s polling cadence
Sentinel (Local Agent)Ping24/7 at the cadence — but never slower than every 30 s, so outages are always caught fast
Sentinel (Local Agent)SNMP bandwidth and errors24/7 at the cadence
Sentinel (Local Agent)CPU / memory / temperature (vendor OIDs)24/7 at the cadence — but never more often than every 60 s (heavier queries)

In Sentinel mode the Agent batches results and pushes them to the cloud, so charts keep filling even when nobody has Observatory open. The push pace follows your fastest device.

Where it is stored

Maintenance is automatic: recent database samples are aggregated into hourly buckets, raw samples older than 30 days are purged, and resolved alerts are removed after 90 days. The 180-day series in the time-series engine are unaffected.

Time ranges

Véase también

Subir