Result fields
Assertion results
Each check evaluates all configured assertions. The result includes per-assertion outcomes:
A check is marked as failed if any assertion with
fail severity fails. Assertions with warn severity don’t cause the check to fail but do record a degraded severity hint.
Protocol-specific details
Check results include protocol-specific data depending on the monitor type.HTTP details
TLS information
WhenverifyTls is enabled, HTTP check results include:
Viewing results
Dashboard
The monitor detail page shows check results in a timeline view with pass/fail status, response times, and assertion breakdowns.CLI
API
Retention
DevHelm retains raw check results based on your plan. Retention is queryable — your plan determines how far back you can read raw results via the API, dashboard, or SDKs. After your tier’s window expires, results are no longer returned by any read path; they are subsequently dropped from storage on the global retention cycle.
Aggregated metrics (uptime percentage, average response time) shown in dashboard summaries are derived from the same window. Daily aggregates are kept longer than the raw window.
If you need to permanently delete a monitor’s data on demand (e.g. for compliance), explicitly delete the monitor — that path purges associated data on request and is independent of plan retention.
Next steps
Monitoring overview
How monitors and check flow work.
Incident policies
How check results trigger incidents.