Result fields
| Field | Type | Description |
|---|---|---|
id | UUID | Unique check result identifier |
timestamp | datetime | When the check ran |
region | string | Probe region that executed the check |
responseTimeMs | integer | Total response time in milliseconds |
passed | boolean | Whether all fail-severity assertions passed |
failureReason | string | Human-readable failure description (null if passed) |
severityHint | string | down, degraded, or null |
Assertion results
Each check evaluates all configured assertions. The result includes per-assertion outcomes:| Field | Type | Description |
|---|---|---|
type | string | Assertion type (e.g., status_code, response_time) |
passed | boolean | Whether this assertion passed |
severity | string | fail or warn |
expected | string | What was expected |
actual | string | What was observed |
message | string | Human-readable result description |
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
| Field | Description |
|---|---|
statusCode | HTTP response status code |
responseHeaders | Key-value map of response headers |
responseBodySnapshot | Truncated response body |
responseSizeBytes | Response body size in bytes |
redirectCount | Number of redirects followed |
redirectTarget | Final URL after redirects |
tlsInfo | TLS certificate and connection details |
TLS information
WhenverifyTls is enabled, HTTP check results include:
| Field | Description |
|---|---|
subjectCn | Certificate common name |
subjectSan | Subject Alternative Names |
issuerCn | Issuer common name |
issuerOrg | Issuer organization |
notBefore | Certificate validity start |
notAfter | Certificate expiry date |
tlsVersion | TLS protocol version (e.g., TLSv1.3) |
cipherSuite | Negotiated cipher suite |
chainValid | Whether the certificate chain is valid |
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.| Plan | Queryable raw retention |
|---|---|
| Free | 90 days |
| Starter | 90 days |
| Pro | 90 days |
| Team | 180 days |
| Business / Enterprise | 180 days |
Next steps
Monitoring overview
How monitors and check flow work.
Incident policies
How check results trigger incidents.