Private probes let you monitor services that are invisible to the public internet — internal APIs, databases behind firewalls, staging environments, and services inside cloud VPCs.
Creating a private probe
Go to Probes → Create Probe:
- Enter a name for the probe (e.g., "AWS Production VPC")
- Pingura generates a unique API token
- You'll see Docker deployment instructions with the token included
Deploying the probe
Deploy the probe using Docker. Pingura provides the exact command with your API token pre-filled.
The probe container is lightweight and connects back to Pingura's central system. Once running, it appears as "Online" in your probes list.
Assigning monitors to a probe
When creating or editing a monitor, select your private probe instead of public regions. The monitor's checks will run from inside your network.
This is useful for:
- Internal APIs and microservices not exposed to the internet
- Databases and caches in private subnets
- Staging and development environments
- Verifying availability from a specific location (e.g., your office network)
- Services behind VPNs or firewalls
Probe health
Your probes dashboard shows each probe's status:
- Online — Probe is connected and actively running checks
- Degraded — Probe is responding but with issues
- Offline — Probe has stopped checking in
If a probe goes offline, assigned monitors will show as having no data until the probe reconnects.
Availability
- Starter — 1 private probe
- Professional — 5 private probes
- Business — 25 private probes