Support set flag and update log-level example usage #939
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
tmorrisonsfx
approved these changes
Nov 12, 2021
mstumpfx
reviewed
Nov 12, 2021
mstumpfx
approved these changes
Nov 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
open-telemetry/opentelemetry-collector@a51bf5a broke
--setsupport for our distribution and open-telemetry/opentelemetry-collector@48a2e01 removed--log-levelsupport from the collector so that setting non-info log level requires manual config changes (read: inconvenient).These changes ~port the
--setproperties parser and use it in our default config provider. Also updates--log-levelusage throughout project to the required--set service.telemetry.logs.levelvalue.