Private Network Monitoring

Why Monitor Private Networks

Cloud-based monitoring tools can only check endpoints that are publicly accessible. But many critical services — databases, internal APIs, message queues, admin panels — live behind firewalls and are invisible to external monitors.

A database that becomes unresponsive, an internal API that starts timing out, or a background job processor that stops processing — these failures can cascade through your system before any public-facing service shows symptoms. Monitoring at the source catches problems earlier.

StatusDude's private agents bridge this gap. Deploy an agent inside your network, and it monitors internal services with the same reliability and alerting you get for public endpoints.

How Private Agents Work

The private agent is an async Python application that runs as a single process. On startup, it fetches its assigned monitors from the StatusDude API. It then runs health checks at the configured intervals, batches the results, and uploads them back to the API.

All communication is outbound HTTPS. The agent polls for configuration changes and pushes results. There's no need to expose any ports or configure inbound firewall rules. This makes deployment trivial even in locked-down environments.

• Async architecture handles 10,000+ monitors per agent instance
• Semaphore-bounded concurrency (default 500 concurrent checks)
• Gzip-compressed batch uploads for minimal bandwidth usage
• Graceful shutdown with pending result flush
• Automatic reconnection on network interruptions

Deployment Options

The agent is distributed as a Docker image, making it easy to deploy in any environment:

• Docker — docker run with environment variables for API URL and key
• Docker Compose — add it to your existing compose stack
• Kubernetes — deploy as a Deployment or DaemonSet with Helm or raw manifests
• Bare metal — run the Python application directly with pip install
• Systemd — run as a system service on Linux servers

What You Can Monitor

The agent supports the same check types as cloud monitors: HTTP, TCP, and heartbeat. This means you can monitor virtually anything inside your network:

• Internal REST APIs and GraphQL endpoints
• PostgreSQL, MySQL, Redis, MongoDB, and other databases (TCP port check)
• Elasticsearch, Kafka, RabbitMQ clusters
• Internal admin panels and dashboards
• Microservices communicating over internal DNS
• Development and staging environments

Agent Health Monitoring

StatusDude monitors the agents themselves. Each agent instance has a heartbeat monitor — if the agent stops reporting, you get an alert. This ensures you're always aware of monitoring blind spots.

Getting Started

Private agents are an organization feature. To get started, create or join an organization in StatusDude, then navigate to your organization settings and open the Agents tab.

Click "New Agent" to create an agent and receive an API key. Use this key to deploy the agent in your private network using Docker, Docker Compose, Kubernetes, or as a standalone process. The agent connects outbound to StatusDude over HTTPS — no inbound firewall rules or port forwarding required.

• Create or join an organization
• Go to Organization Settings → Agents tab
• Create a new agent and copy the API key
• Deploy using Docker or Helm:

docker run -e STATUSDUDE_API_KEY=your_key statusdude/agent

helm install statusdude-agent oci://docker.io/statusdude/statusdude-agent --set apiKey=your_key