Opyntel
Dokploy

Dokploy monitoring: all your Dokploy apps in one dashboard

Dokploy does not monitor remote servers and keeps metrics 2 days by default. Opyntel’s Dokploy monitoring shows every app on every server at a glance, plus the other systems you run.

See how it works
Built in vs Opyntel

Dokploy on its own, and Dokploy with Opyntel

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

All your services in one dashboard

On Dokploy

Dokploy deploys apps to several remote servers, but its remote servers docs say remote server monitoring is the one feature not supported. The monitoring docs show a server view and a services view and describe the server monitoring setup as a Dokploy Cloud feature.

With Opyntel

Opyntel puts the full list of your services in one table, every app on every server, down and degraded first. One docker run of the Opyntel agent on each server fills in what Dokploy does not watch, so you see it all at a glance, Dokploy plus the other systems you run.

Alerts per service, and when it recovers

On Dokploy

Dokploy alerts when CPU or memory passes a percentage threshold, measured on the whole server rather than on individual services, through your enabled notification providers. Its other notifications cover app deploys, build errors, database and volume backups, Docker cleanup and Dokploy restarts, across 12 providers including Slack, Telegram, Discord and email.

With Opyntel

Opyntel alerts per service as well as per server: a service or container down, CPU or memory past your threshold, a disk nearly full or on track to fill, and on Pro custom rules per service, project or environment. Every alert notifies when it fires and again when it recovers, by email, Slack or SMS depending on your plan.

Memory and disk from inside every server

On Dokploy

The monitoring docs name CPU and memory as the alert thresholds for server and container metrics. Each server needs its own metrics token and port 4500 open for metrics to reach Dokploy.

With Opyntel

The Opyntel agent reports memory, disk fill level, load and per-container CPU, memory and restarts from every server, remote ones included. It sends over outbound HTTPS only and needs no inbound port.

History

On Dokploy

Dokploy keeps server metrics for 2 days by default, removed by a cron job, and you can change the retention in days. Server and container data refresh every 20 seconds by default.

With Opyntel

Opyntel keeps the same server and container history for 30 days on the free plan, a year on Pro and unlimited on Enterprise. It sits outside your servers and does not grow their disks.

Latency percentiles and error rate

On Dokploy

The monitoring docs describe server and container metrics with CPU and memory thresholds. 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, in the same table as CPU and memory. It alerts when the error rate or p95 latency passes your threshold.

Deploys on one timeline

On Dokploy

Dokploy sends notifications when an app deploys or a build fails, to the providers you configure, across 12 providers.

With Opyntel

Opyntel puts every deploy with its commit on one activity timeline, across your Dokploy servers and the other platforms you run. A failing service sits next to the deploy that came before it.

Setup

How to set up Dokploy monitoring with Opyntel

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

  1. Generate a Dokploy API token
    In Dokploy, open your profile settings and generate a token in the API/CLI section. A user who is not an administrator needs an administrator to allow tokens first.
    Generate a Dokploy API token
  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. Paste the token and start the agent
    Paste the token with your Dokploy URL. For memory, disk fill level and per-container CPU and memory, run the docker run command your dashboard shows on each of your servers: the agent sends over outbound HTTPS only and opens no port.
  4. See Dokploy in one dashboard
    Dokploy 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

Dokploy questions, answered

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

Its main process exits and Docker’s restart policy brings it back; the exit code tells you why. Why a Docker container keeps restarting.

Dokploy’s monitoring shows server and container memory; on the server, free -h and docker stats show the same. Opyntel alerts when memory passes your threshold. Check memory usage on a Linux server.

Traefik requests the certificate once DNS points at the server and port 80 is open; behind the Cloudflare proxy, use Cloudflare’s certificate instead. Opyntel alerts before a certificate expires. Fix an expired or missing SSL certificate.

The container reached its open files limit. Raise it with ulimits in the Compose file, then check for a leak. Opyntel alerts when open files pass your threshold. Fix too many open files in a container.

Dokploy logs every run of a schedule job. Opyntel alerts when one fails or does not run. Why a cron job is not running.

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