Knowledge Base / How to

How to

Troubleshooting telemetry

Check access and evidence separately.

Configured access, a successful connection and enough evidence are different states. Kubernetes API access and Prometheus telemetry acquisition are independent; success in one does not establish the other.

What to do next

Start with the named acquisition problem or evidence gap. Newly enabled telemetry cannot establish coverage before collection began. Do not interpret an empty history as proof that no pressure occurred.

Back to Knowledge Base

Check monitoring before waiting longer.

Confirm the cluster is running and Managed Prometheus is collecting the required CPU, memory, and ownership series. Review the most recent acquisition time and the exact missing-data reason. Authentication success does not prove sufficient history.

Troubleshoot authorization and metrics separately · Understand usable evidence