Metrics & Charts
Metrics power monitor detail charts, status page charts, uptime summaries, and success criteria. Testable records standard metrics for checks and can capture custom metrics from custom scenarios and heartbeat JSON bodies.
Where Metrics Appear
- Monitor list - Uptime bars and percentage summaries.
- Monitor detail - Time-series charts, averages, minimums, maximums, incidents, checks, pings, and comments.
- Status pages - Optional uptime percentages, uptime bar charts, metric line charts, and overall stats.
- Success criteria - Metric thresholds used to determine pass/fail.
Default Metrics
Organization monitor settings define default metrics to capture and display. Defaults include first received time, success percentage, and assertion pass percentage. These can be changed globally and overridden per monitor.
Heartbeat Metrics
Heartbeat monitors can capture metrics from JSON POST bodies when Pass metrics with body of heartbeats is enabled. Those metrics can be selected in the monitor chart and shown on status page detail pages when metric charts are enabled.
Success Criteria
Success criteria compare metrics to thresholds using operators such as greater than, less than, equals, or not equals. Criteria can be configured as organization defaults, by monitor type, by custom scenario type, or per monitor.
Time Ranges
Common time ranges include last hour, last 24 hours, 7 days, 30 days, 90 days, 365 days, recent, and custom ranges depending on the view. Status pages can also limit maximum history and set default ranges separately for incidents, uptime, announcements, and metrics.
Best Practices
- Keep default metrics small and useful so monitor pages stay focused.
- Use success criteria for warning signs such as latency degradation, not only total failures.
- Capture heartbeat metrics with stable names and units such as
freeMemory[bytes]. - On customer-facing status pages, expose only metrics that help users understand service health.