etcdhttp/metrics.go: exclude alarms from health check conditionally with ?exclude=NOSPACE
#12880
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Exclude alarms from health check with
?exclude=NOSPACE
Similar to kubernetes excludes specific checks
https://kubernetes.io/docs/reference/using-api/health-checks/#api-endpoints-for-health
The motivation is to exclude NOSPACE alarms in etcd supervisor or peer to peer health checks.
Testing
Added unit test against serverV2 to verify the logic due to v3
*etcdserver.EtcdServer
is hard to mock out.Unit test output