Server resource monitoring for dm components
Open
Nobody has claimed this yet.
component/dm
type/question
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
We need to add server monitoring to dm-worker and dm master to check whether there are server resource bottlenecks in each component of dm in high concurrency scenarios
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 the dm-worker and dm master components and checking their existing monitoring or metrics entry points. Clarify which server resources must be measured and how bottlenecks should be reported under high-concurrency workloads; done means both components expose the agreed monitoring coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100