Metric shows no data

Q: Step 1: confirm an agent is assigned

In the console, open **Metrics**, then the metric in question. The detail page shows the assigned agent. If the field is empty, the metric is defined but no agent is collecting it. Set the **Agent** field, save, and wait one push interval (default one minute). The cloud's metric-definitions endpoint refreshes the agent's assignment every five minutes; restart the agent to pull the updated list immediately.

Q: Step 2: confirm the agent is running

Open **Agents** in the console and verify the assigned agent shows status **running**. If it shows **stopped**, walk the stalled agent diagnosis (/agent/guides/diagnose-stalled-agent).

Q: Step 3: confirm the probe is succeeding

If the metric reports no_data rather than no value at all, the agent ran the probe and the probe failed. The metric's detail page shows the latest reason string. | reason substring | Probable cause | |---|---| | ECONNREFUSED | The target's port is closed or the host is unreachable. Verify network reachability from the agent's host. | | ENOTFOUND | DNS resolution failed. Check PROMETHEUS_SERVER_URL or the probe's target hostname. | | ETIMEDOUT | Target is reachable but did not respond within the configured timeout. | | HTTP 401 / HTTP 403 | Authentication or authorization failed against the probe target. | | prometheus query empty | The PromQL returned no series. The series name or label match probably does not exist. | For Prometheus probes, run the query directly against the Prometheus server (the same URL the agent uses) and confirm it returns a single scalar.

Q: Step 4: confirm the threshold rule is correct

A metric that reports values but with status unknown typically has thresholds that do not cover the value range. Open the metric and verify: - healthy_under / healthy_over define a band the value can reach. - unhealthy_under / unhealthy_over define the failure band. - Comparison operators are strict (over is >, under is <, equal is =). A value exactly on a boundary does not match that band.

Q: Step 5: confirm the dashboard view

If the metric reports values in the console's metric detail page but a status page shows no data, verify: - The metric is on the page (open the page builder). - The metric's is_public flag is set (visible on the metric edit page). Each probe type has a dedicated configuration guide: Prometheus (/agent/guides/prometheus-source), HTTP (/agent/guides/http-probes), TCP (/agent/guides/tcp-probes), DNS (/agent/guides/dns-probes), TLS certificate (/agent/guides/tls-cert-probes). Each one covers the probe-specific failure modes in detail.

A metric with no recent value is almost always one of three problems: no agent is assigned to the metric, the assigned agent is not running, or the agent is running but the probe itself returns an error.

Step 1: confirm an agent is assigned

In the console, open Metrics, then the metric in question. The detail page shows the assigned agent. If the field is empty, the metric is defined but no agent is collecting it.

Set the Agent field, save, and wait one push interval (default one minute). The cloud's metric-definitions endpoint refreshes the agent's assignment every five minutes; restart the agent to pull the updated list immediately.

Step 2: confirm the agent is running

Open Agents in the console and verify the assigned agent shows status running. If it shows stopped, walk the stalled agent diagnosis.

Step 3: confirm the probe is succeeding

If the metric reports no_data rather than no value at all, the agent ran the probe and the probe failed. The metric's detail page shows the latest reason string.

`reason` substring	Probable cause
`ECONNREFUSED`	The target's port is closed or the host is unreachable. Verify network reachability from the agent's host.
`ENOTFOUND`	DNS resolution failed. Check `PROMETHEUS_SERVER_URL` or the probe's target hostname.
`ETIMEDOUT`	Target is reachable but did not respond within the configured timeout.
`HTTP 401` / `HTTP 403`	Authentication or authorization failed against the probe target.
`prometheus query empty`	The PromQL returned no series. The series name or label match probably does not exist.

For Prometheus probes, run the query directly against the Prometheus server (the same URL the agent uses) and confirm it returns a single scalar.

Step 4: confirm the threshold rule is correct

A metric that reports values but with status unknown typically has thresholds that do not cover the value range. Open the metric and verify:

healthy_under / healthy_over define a band the value can reach.
unhealthy_under / unhealthy_over define the failure band.
Comparison operators are strict (over is >, under is <, equal is =). A value exactly on a boundary does not match that band.

Step 5: confirm the dashboard view

If the metric reports values in the console's metric detail page but a status page shows no data, verify:

The metric is on the page (open the page builder).
The metric's is_public flag is set (visible on the metric edit page).