Check for *_exporter before import ansible deployed cluster
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:
For an ansible deployed tidb cluster, if the node_exporter or blackbox_exporter is not deployed properly, the imported cluster may fail to upgrade in later operations.
An example of user report about this case is available on AskTUG.
Describe the feature you'd like:
We need to find a way to either:
- Check for broken node_exporter or blackbox_exporter before importing the cluster, or
- Automatically deploy the agents after imported the cluster
Describe alternatives you've considered:
We have the automatically upgrade process for prometheus and alertmanager for imported cluster, maybe we can do this in a similar way?
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
No files, entry points, or tests are named. Start by tracing the imported-cluster flow and comparing it with the existing Prometheus and Alertmanager automatic upgrade process. Define whether import should validate node_exporter and blackbox_exporter or deploy them, then establish tests and acceptance criteria for a failed or missing agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, prometheus
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100