Self-Hosted Docker Monitoring
Metrics, health, alerts — on your infrastructure
Monitoring self-hosted infrastructure usually means one of two contortions: shipping your metrics to a SaaS you adopted specifically to avoid depending on, or assembling and operating a Prometheus–Grafana–Alertmanager stack that quickly becomes its own service to babysit.
BridgePort ships monitoring as part of the control plane. The same tool that deploys your services watches them: server metrics, container stats, database metrics, four kinds of health checks, and notifications — with history stored in your own database and nothing leaving your infrastructure.
How it works
Connect servers
SSH mode needs nothing installed and collects server metrics on a polling cycle (default: every 5 minutes).
Enable the agent where you want more
Flip a server to agent mode and BridgePort auto-deploys its lightweight Go agent over SSH — real-time metrics push, container stats, and process snapshots, typically live within 30 seconds.
Add health checks
Container, URL, TCP, and TLS-certificate checks with bounce protection so a single blip does not page anyone. Results feed service status and history.
Route alerts
Notification types cover deploys, health transitions, and system events; outgoing webhooks (with HMAC signatures and retries) forward events to Slack, PagerDuty, or anything with a URL.
What you get
Server metrics
CPU, memory, disk, and load per server — over SSH with zero install, or in real time via the agent.
Server monitoring →Container & service metrics
Docker stats per service deployment, tied to the service model rather than anonymous container IDs.
Service monitoring →Database monitoring
Plugin-driven collectors gather size, activity, and performance metrics from your databases on their own interval.
Database monitoring →Four kinds of health checks
Container state, URL/HTTP, TCP port, and TLS certificate expiry — with bounce protection against flapping.
Health checks →Notifications & webhooks
Built-in notification channels plus signed outgoing webhooks with retry behavior for external systems.
Notifications →Your data, your retention
History lives in BridgePort’s embedded database on your infrastructure, with retention-based cleanup you configure.
System settings →Frequently asked questions
Do I need to run Prometheus or Grafana?
No. Metrics collection, storage, charts, and alerting are built into BridgePort. If you already run a metrics stack, BridgePort complements it with deployment-aware health checks and event webhooks.
Is an agent required for monitoring?
No — SSH mode collects server metrics with nothing installed. The optional Go agent upgrades a server to real-time push metrics, container stats, and process snapshots, and BridgePort deploys it automatically.
Can BridgePort alert my team in Slack or PagerDuty?
Yes. Notification events can be forwarded through outgoing webhooks — signed, filtered by type and environment, and retried on failure — to any system that accepts an HTTP request.
Does any monitoring data leave my infrastructure?
No. BridgePort is fully self-hosted; metrics and health history are stored in its embedded SQLite database on your own server, with configurable retention.