Ensure network connectivity and availability across your infrastructure
Exemplar
How this capability fits the Exemplar platform—not a standalone point tool, but part of how your org runs production and talks about it.
When latency spikes or paths flap, application metrics alone rarely show whether the network layer is at fault.
Exemplar adds lightweight reachability and latency signals so you can separate “app regression” from “routing or host down.”
ICMP-based checks with latency and loss trends, including multi-region perspectives where you need geographic coverage.
Ping and heartbeat-style checks complement HTTP monitoring: good for internal jump hosts, VPN concentrators, and dependencies that do not speak HTTP.
Define hosts or internal endpoints in the console; align checks with the blast radius you model in your service catalog.
Use ping trends during incident triage alongside vendor status and app traces to narrow root cause before paging deep application teams.
Official documentation on docs.exemplar.dev for this capability.
Open developer guide (opens in a new tab)Related posts on exemplar.dev.
APM and telemetry explain behavior under traffic; synthetics answer a different question—mature teams use both. How Exemplar complements observability with probes, SSL, vendor feeds, incidents, and status boards.