Netcracker / Netcracker/DRNavigator
Check necesisty of site_manager_health metric
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Now we have site_manager_health metric, that shows, if health check passed:
https://github.com/Netcracker/DRNavigator/blob/main/site-manager.py#L34
Additionally after #123 will add paas_geo_monitor_health metric.
Those metrics are 0 by default and become to be 1 after the first successful health check, but not on the contrary.
Need to check, if kubernetes/prometheus has more appropriate mechanisms for health check, e.g. metrics for readness/liveness probes.
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 at site-manager.py#L34 and inspect how site_manager_health is produced. Compare that metric, and the planned paas_geo_monitor_health metric from #123, with Kubernetes readiness/liveness probes and Prometheus mechanisms. Done means determining whether these metrics should remain and documenting the appropriate health-check approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, prometheus, python
- Domain
- devops, observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100