Dokploy / Dokploy/dokploy

Add monitoring stats for all remote servers, not only the Dokploy server

Open
#4,420 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

The Monitoring page currently only shows usage stats for the main Dokploy server.

When multiple remote servers are connected, there is no way to view CPU, memory, disk, or Docker disk usage for each server from Dokploy. This makes it harder to monitor server health and decide where to deploy services.

Describe the solution you'd like

Show monitoring stats for all connected remote servers, not only the Dokploy server.

Useful metrics would include:

  • CPU usage
  • Memory usage
  • Disk usage
  • Docker disk usage
  • Server status / availability

This could be shown as separate cards/charts per server or through a server selector on the Monitoring page.

Describe alternatives you've considered

The current workaround is manually SSH-ing into each server and checking stats with tools like htop, df, docker system df, or using external monitoring tools.

Additional context

I have multiple servers connected in Dokploy, such as application, database, staging, and monitoring servers, but only the Dokploy server usage is shown.

Will you send a PR to implement it?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by tracing the existing Monitoring page flow for the main Dokploy server and how connected remote servers are represented. Define how CPU, memory, disk, Docker disk usage, and availability should be collected and displayed per server, then verify that all connected servers appear with accurate status and metrics.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
infrastructure, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.