Get a probe test result
Returns 202 while the agent has not answered, then the same result testProbe returns. Results are kept for about a day. A key with write:metrics or write:config may call it; jobs of other organizations return 404.
Authorizations
An organization API key (obs_pub_…) sent as Authorization: Bearer <key>. Each key carries scopes; an endpoint lists the scope it needs. read:change_events is reserved: keys can carry it, but no endpoint needs it yet.
Path Parameters
job_id from a 202 testProbe response.
Response
the probe ran
What the probe measured, in unit. null when it got no value (see reason).
Unit of value (ms, %, days, s, B/s), or null for a bare number. Same rules as a metric's unit.
The status these thresholds give the value; no_data when the probe got no value. null when a value was measured but thresholds were not all given.
healthy, degraded, unhealthy, no_data, null How long the probe took, in milliseconds.
agent: ran on the agent's network with its secrets. cloud: a public HTTP check run from Observer's cloud.
agent, cloud What the value is, in words.
Why there is no value: the agent's reason code (e.g. ETIMEDOUT, unexpected_status:503). null on success.
Short human description of reason.
What usually causes reason and how to fix it.
The agent job (agent mode only).
Cloud mode only: header_refs names that were not sent, because their values live on an agent host.

