Fix: WithPrometheus should bind client metrics #21
+7
−0
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.
Summary
WithPrometheus.WithPrometheusonly stored the registerer and never bound metrics, acting as a no-op.Changes
client/client.go:github.com/drand/go-clients/internal/metrics.makeClient), ifcfg.prometheus != nil, callmetrics.RegisterClientMetrics(cfg.prometheus)to bind all client metrics.Why
WithPrometheusbehaves as documented/expected and client metrics become observable/exported.Testing
go build ./...andgo test ./...: all green..Backward compatibility
Notes
Closes #6