support to reuse prometheus for other components that is not deployed by tiup-cluster
Open
Nobody has claimed this yet.
type/feature-request
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
Why the featue is needed:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 tiup repository and the existing tiup-cluster Prometheus deployment flow. Define how Prometheus should be reused for components that tiup-cluster does not deploy, including the required configuration and adoption behavior. Done means the feature scope is specified and supported by implementation and validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100