Can directly modify the information of monitoring related components
Nobody has claimed this yet.
- 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:
Each time TiUP is started, it will overwrite the original service, which will cause the manually modified service to be overwritten when it is restarted
Describe the feature you'd like:
Many users have the need to modify the ports or directories of components related to monitoring, and the use of these components does not affect the use of the cluster. It is recommended to modify directly.
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
The issue names no files, tests, or entry points, so first locate TiUP's startup and monitoring-component configuration logic. Clarify which ports or directories must remain editable and define how startup should preserve those changes, then add tests demonstrating the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100