support deploying node_exporter with tiup playground
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Describe the feature you'd like:
Currently, tiup playground can deploy a prometheous with --monitor command option. Node exporter is also a important component in tidb monitoring system.
Some TiDB features rely on node_exporter such as sql diagnose. For example, https://github.com/pingcap/tidb/pull/17671/files#diff-bc46c5da5501515ea44a6d9abec45b22R328. TiDB reads metric node_total_memory to check something.
In summary, it would be great if tiup playground can deploy a node_exporter.
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 tracing tiup playground's --monitor handling and its existing Prometheus deployment path. Check the linked TiDB monitoring documentation for how node_exporter is deployed, then verify that playground can deploy it alongside Prometheus and provide the cited node_total_memory metric.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100