Recent core↔poller visibility outages (Phase 3, store-and-forward). Newest first, capped. A read error degrades to an empty list rather than failing the Pollers page.
const url = 'https://example.com/api/v1/monitoring-gaps';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/monitoring-gaps \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Recent core↔poller visibility outages, newest first
One monitoring_gaps row (API shape). A gap is one core↔poller visibility outage: core
stopped hearing from the poller (partition or the poller went down) and later saw it again. If the
poller was alive but partitioned, its store-and-forward buffer backfills the metrics for the
window on reconnect (Phase 3); alerts are not backfilled (they resume from “now”).
object
Gap length in seconds (UI convenience).
End of the gap window (RFC 3339 — core heard from it again).
Row id.
Passive listeners the poller had bound when the gap began (e.g. syslog:514, trap:162).
Empty ⇒ the poller had none, so the gap cost no passive data. Non-empty ⇒ whatever those listeners would have received in the window is gone: syslog, traps and flow exports are fire-and-forget, so unlike active polling there is no buffer to backfill from. (SNMP informs are the exception — the sender retries until acknowledged.)
The poller whose visibility lapsed.
Pool it serves.
When core recorded the gap (RFC 3339).
Start of the gap window (RFC 3339 — core’s last contact before the outage).
Examplegenerated
[ { "duration_secs": 1, "ended_at": "example", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "listeners": [ "example" ], "poller_id": "example", "pool": "example", "recorded_at": "example", "started_at": "example" }]No valid bearer token
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}Role lacks the View permission
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}Skeleton mode: no durable poller store
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}