This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
fix: only start prometheus metrics in one place #2954
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the `IPFS_MONITORING` env var is set, we use prometheus to collect resource usage stats. We only need to set them up in one place though. Fixes #2019
mistakia
pushed a commit
to mistakia/js-ipfs
that referenced
this pull request
Apr 3, 2020
When the `IPFS_MONITORING` env var is set, we use prometheus to collect resource usage stats. We only need to set them up in one place though. Fixes ipfs#2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When the
IPFS_MONITORINGenv var is set, we use prometheus to collect resource usage stats. We only need to set it up in one place though.Fixes #2019