Troubleshoot the private probe
If you are encountering any issues with your private probe, you can take the following troubleshooting steps.
Review DEBUG logs
-
Set the log level to DEBUG within your
PRIVATE_PROBE_CONFIG_FILE. -
Check the following Docker Container Logs for these key metrics.
probeID is reviewable in the Container logs after the private probe starts. traceID is reviewable in the Container logs if an error occurs. Example: probeID
{"time":"2025-08-12T13:25:18.402069508Z","level":"INFO","msg":"Probe registered","probeID":"06ddbb70-0048-4642-aad8-f26ca83d0948"}
Example: traceID
{"time":"2025-08-12T13:25:18.516435626Z","level":"ERROR","msg":"something went wrong","error":"rpc error: code = NotFound desc = not found, trace id: ec03bf06cb97904bd0ce4bbda9946051"}
Monitor the private probe with SolarWinds Observability
For private probes deployed in Cloud environments:
Use SolarWinds Observability to monitor your Cloud Providers infrastructure and view useful metrics generated by the Cloud Provider. See infrastructure monitoring for instructions regarding your Cloud Provider.
For private probes deployed in Kubernetes environments:
Use SolarWinds Observability to monitor your Kubernetes cluster to view basic METRICS and LOGS. See Kubernetes monitoring.
PING doesn't work for Private Probe on Azure Kubernetes Cluster
Enable the Public IPs per node in the Node pool configuration.