Cherry-pick opt-in telemetry (#2193) #2676
Merged
Conversation
This file contains hidden or 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
Make telemetry opt-in, with env.MC_TELEMETRY set to 1 or true
eranrund
approved these changes
Oct 7, 2022
cbeck88
approved these changes
Oct 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Make telemetry opt-in, with env.MC_TELEMETRY set to 1 or true.
Motivation
Currently, running a consensus network without a telemetry configuration causes a ton of spurious logs. This PR cherry-picks inverting that situation (makes telemetry off by default, requiring
MC_TELEMETRY=1to enable).