Synthetic monitors

Synthetic monitors are Central-oriented HTTP availability/latency checks run by the collector — not by application agents.

Configure under Configuration → Synthetic monitors. View results on the Synthetic monitors navbar page (Central UI).

On a schedule, Central issues HTTP GET requests to URLs you define (optional basic auth, proxy, SSL trust options). Results are stored as rollups and charted like other Central metrics.

Use them for:

• External endpoint reachability
• Simple latency trends independent of in-app instrumentation
• Alert conditions when a URL is slow or failing

Synthetic latency is stored in milliseconds.

A flat line at ~60000 ms usually means timeout (Central’s ping timeout is 60 seconds), not real application latency. Investigate network, DNS, TLS, or the target being down before tuning app performance.

Alert definitions can use synthetic monitor metrics as conditions — same alert/incident flow as transaction or gauge alerts. See Alerts and incidents.

Synthetic monitors require Central (collector + Cassandra). They do not run in embedded-only deployments.

• Alerts and incidents
• Central Collector Installation
• HTTP API and export