Opyntel
CapRover

CapRover monitoring: all your CapRover apps in one dashboard

CapRover shows app CPU and memory in its dashboard and its monitoring docs describe no alerts. Opyntel’s CapRover monitoring adds alert rules and every node at a glance, plus the other systems you run.

See how it works
Built in vs Opyntel

CapRover on its own, and CapRover with Opyntel

Feature by feature, the biggest gaps first: what CapRover gives you, and what you get in one dashboard with Opyntel.

All your services in one dashboard

On CapRover

CapRover shows app CPU and memory use in the Captain Monitoring menu of its dashboard, and you can turn on NetData to monitor the server. A cluster adds worker nodes through Docker Swarm, and the cluster docs describe no monitoring of those nodes.

With Opyntel

Opyntel puts the full list of your services in one table, every app and every node, down and degraded first. You see it all at a glance, CapRover plus the other systems you run, in one place.

Alerts when it goes down, and when it recovers

On CapRover

The resource monitoring docs cover the Captain Monitoring menu and NetData. They describe no alerts.

With Opyntel

Opyntel alerts out of the box when a container goes down, memory or CPU stays high, or a disk is nearly full or on track to fill, with custom rules per service on Pro. Every alert notifies when it fires and again when it recovers, by email, Slack or SMS depending on your plan.

Memory and disk on every node

On CapRover

NetData is an optional tool that monitors the server it runs on. Nodes join the cluster over SSH, and the cluster docs describe no node monitoring.

With Opyntel

The Opyntel agent runs with one docker run on each node and reports memory, disk fill level, load and per-container CPU, memory and restarts. It sends over outbound HTTPS only and needs no inbound port.

Latency percentiles and error rate

On CapRover

The resource monitoring docs answer whether an app is eating memory or CPU. They describe no request, latency or error-rate metrics.

With Opyntel

Opyntel shows requests, status classes, p50, p95 and p99 latency and the 5xx error rate for every public service, beside its CPU and memory. It alerts when the error rate or p95 latency passes your threshold.

History

On CapRover

The resource monitoring docs give no history or retention period for the Captain Monitoring view.

With Opyntel

Opyntel keeps CPU, memory, disk and container history for 30 days on the free plan, a year on Pro and unlimited on Enterprise, so you can look back at the hour a node filled up.

Setup

How to set up CapRover monitoring with Opyntel

CapRover monitoring in four steps: from CapRover to one dashboard with everything else you run.

  1. List your CapRover nodes
    CapRover runs on Docker Swarm, and the Cluster section of its dashboard lists every node. Opyntel reads CapRover through its agent, once on each node, so it never needs your CapRover password.
    CapRover cluster nodes
  2. Sign in to Opyntel
    Open your Opyntel dashboard and add a source. Accounts start from the waitlist, so join it to get yours.
  3. Run the agent on each node
    Copy the docker run command from your dashboard and run it on every node. It reports each container’s CPU, memory and restarts and the node’s memory and disk, over outbound HTTPS only.
  4. See CapRover in one dashboard
    CapRover monitoring lands next to the other platforms you run: every service and server sits in one dashboard, down and degraded first, with default alert rules on from the start.

Don’t see your platform? From your Opyntel account you can request an integration with more platforms. Until then, and tell us which one you run on.

FAQ

CapRover questions, answered

Short answers; some link to a guide that goes into detail.

Docker Swarm starts a new container whenever the old one exits, so a crash on start loops. The app logs and exit code show why. Opyntel alerts when restarts pass your threshold. Why a Docker container keeps restarting.

CapRover’s NetData monitoring shows memory, and free -h and docker stats show it on the server. Opyntel alerts when memory passes your threshold. Check memory usage on a Linux server.

CapRover renews its Let’s Encrypt certificates over port 80, so a closed port or a moved domain stops renewal. Opyntel alerts before a certificate expires. Renew an expired SSL certificate.

Each app’s Deployment tab has a View App Logs button. On the server, docker service logs srv-captain--<app> prints the same log.

The alerts your platform doesn’t send.

One dashboard for everything you run, with the alerts your platforms leave out. Read-only, nothing to install in your apps.

See how it works