Checkmate watches the containers your stack runs on: status, health checks, restart events and resource usage, next to the uptime monitors for the services inside them.
A container can exit at 3am and be restarted by its policy before anyone notices, or stay down until a customer does. Docker monitors track container state plus the health checks your images define, so either way there is a record and an alert.
If an image ships a HEALTHCHECK, Checkmate reads it. Unhealthy is the warning you get before stopped.
Restart events are reported alongside host metrics, so a container bouncing every few minutes stops hiding behind its restart policy.
The pattern is visible in history: one restart after a deploy is noise, 40 an hour is a bug.
Per-container resource usage, reported through the Capture agent next to the host's own CPU, memory and disk. When a machine runs hot, the answer to 'which one is it' is on the same page.
That beats SSHing in to run docker stats while the pager keeps buzzing.
Your services live in containers on one or two boxes. Watch all of them without adding a heavyweight orchestration layer.
A VPS running a compose stack is a common production setup. Container health, host health and endpoint uptime in one dashboard covers it.
20 containers accumulate fast. Get a straight answer to which ones are up, unhealthy or stuck in a restart loop.
Docker monitors sit next to HTTP, ping and the rest. Add one per container you care about, set the interval and route its alerts like any other monitor.
The HEALTHCHECK your image already defines is the best signal of container wellbeing. Checkmate surfaces it instead of inventing a parallel definition of healthy.
The container being up and the service inside answering are different facts. Run a Docker monitor next to an HTTP monitor for the same app, and know which layer broke.
The whole platform ships as a small set of containers with a compose file. Monitoring containers from containers is the normal setup here.
Add a Docker monitor for a container. Checkmate tracks its status and health check results on the schedule you set. Restart events and resource usage appear alongside. Alerts route through your notification channels.
Yes. Restart events are recorded with the host metrics, so a restart loop shows up as a visible pattern and a status change fires your alert channels.
Yes, through the Capture agent, which reports per-container usage next to host-level CPU, memory and disk. Finding the container that is eating a machine takes one look.
No. Checkmate watches containers and hosts, not orchestrator control planes. If you run plain Docker or compose stacks, it fits. For Kubernetes-native observability you'll want a Kubernetes-native tool.
Yes. It ships as a small set of containers: pull the compose file, run it and the dashboard is up. About 1 GB of RAM on any Docker host is enough to start.
Yes. Open source under AGPL-3.0, self-hosted, with no container or host limits.
Websites and APIs checked from 6 continents.
Certificate expiry caught before browsers complain.
CPU, memory, disk and network via the Capture agent.
More than 100 game types over native protocols.
Branded public pages served from your own instance.
12 native channels, from email to PagerDuty.
All featuresCheckmate is open source under AGPL-3.0. Self-host it and this feature ships free, on your servers, with your data.