pingcap / pingcap/tidb-operator
Expose key metrics to Prometheus
Open
Nobody has claimed this yet.
area/monitor
enhancement
lifecycle/frozen
status/WIP
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
For better diagnose tidb-operator, we should monitor it with Prometheus. Some key metrics like pod scheduling, upgrading time etc need to be exposed.
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 reviewing the tidb-operator code responsible for managing TiDB clusters and determine how metrics are currently exposed, if at all. Clarify which key metrics are required, especially pod scheduling and upgrade duration, then verify that the resulting metrics can be collected by Prometheus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100