loki/wal: fix panic for duplicate registered metrics #5705
Merged
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.
PR Description
The original issue in #5414 is easily reproducible by changing the configuration of a
loki.write
component and hitting the reload endpoint, as the NewWatcherMetrics will attempt to re-register the same set of metrics.Which issue(s) this PR fixes
Fixes #5414
Notes to the Reviewer
Another possible fix would be to create these metrics at the top-level, when creating a New component and propagate a pointer to the metrics struct down to here. Both solutions could work, but for now, this is what we've mainly been doing in loki.* components when forklifting Promtail code, so an argument can be made to leave this as-is for now to not trip off people when trying to bring new Promtail code in.
PR Checklist