Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/observe-and-act/testing/synthetic-monitoring/set-up/set-up-private-probes/troubleshoot.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/observe-and-act/testing/synthetic-monitoring/set-up/set-up-private-probes/troubleshoot/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Troubleshoot private probes
If a Synthetic Monitoring private probe isn’t connecting or working as expected, use the following checks to review the agent’s configuration, logs, and metrics. For failures reported by a check, refer to Troubleshoot a failing check.
- Check the probe version using the
-versionflag and make sure you are running a supported version. - Make sure the probe has a valid probe access token.
- Make sure the probe can connect to the Synthetic Monitoring API server.
- Run the Synthetic Monitoring Agent in debug mode with the
-debugand-verboseflags and check for errors in the logs. - Check the Synthetic Monitoring Agent metrics. The default address for Synthetic Monitoring Agent Prometheus metrics is
localhost:4050/metrics. - If clustered agents don’t form a single cluster:
- Check the agent logs for messages with
subsystem=cluster. Thecluster peers changedmessage lists the current members. bootstrapping single-node ringmeans the agent couldn’t find or join any peer. Check-cluster-join-addresses, DNS resolution, and that TCP port7946is open between agents.address did not resolvemeans one of the join addresses didn’t resolve to any IP address.- Make sure every agent uses the same
-cluster-nameand-cluster-listen-port. - Make sure the other agents can reach each agent’s advertise address. Set
-cluster-advertise-addressor-cluster-advertise-interfacesif needed.
- Check the agent logs for messages with
- If some scripted or browser checks never run in a cluster, make sure every agent has the same feature flags enabled, uses the same image variant, and has the same browser pool configuration. Refer to Cluster requirements.
- If browser checks fail with a browser pool:
- Check the agent logs for messages with
subsystem=browser_pool. - If
sm_agent_browser_pool_acquires_total{result="exhausted"}increases, no browser pool instance was free. Add instances. - If
sm_agent_browser_pool_instancesis0, the agent didn’t find any instance. Check-browser-pool-addressesand DNS resolution, and make sure thecrocochromeService is headless. - If
sm_agent_browser_pool_probes_total{result="error"}increases, the agent can’t reach the instances or they don’t support session acquisition. Check that TCP port8080is open from the agents and that the instances runcrocochromev0.13.0or later.
- Check the agent logs for messages with
If you are still facing issues with Private Probes, ask for help in the community forum. Refer to Account types and support available for Grafana Cloud users for more information.
Was this page helpful?
Related resources from Grafana Labs


