SWAP monitoring
Open
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?
I have swap added to my server, this is mainly because most of my services will be dormant, and I'd like to have efficient use of my server memory.
Describe the solution you'd like
I want to have SWAP usage (or %) in the monitoring, so I can see when my server 'really' runs out of memory.
Describe alternatives you've considered
Doing the monitoring myself, but that kinda defeats the purpose of dokploy
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Dokploy's existing monitoring implementation and the entry point that collects server memory metrics. Confirm how monitoring data is exposed, then add SWAP usage or percentage alongside the existing memory measurements and verify it appears in the monitoring view.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100