Consul version metric improvements
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Feature Description
Consul version metric currently exports version name and ONLY on servers.
It would be good if it exported version_sha, and also on clients.
#### Use Case(s)
for exporting metrics on clients - we would like to monitor the state of 80k+ consul deployment, which versions they are running and anomalies related to version change.
for exporting sha - we use a fork of consul to apply security patches, same as above - we would like to monitor versions including sha changes.
Happy to work on this feature if it sounds reasonable
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the existing Consul version metric implementation and its server-only export path, then inspect related metric tests if available; done means exporting version_sha and the version metric for clients as well as servers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100