feat(opentelemetry-node): include OTEL_ and ELASTIC_OTEL_ envvars in preamble log.info#1151
Merged
feat(opentelemetry-node): include OTEL_ and ELASTIC_OTEL_ envvars in preamble log.info#1151
Conversation
…preamble log.info This includes all likely to be relevant envvars in the preamble log message to help with clarity and debugging. The *value* of envvars are included if they are on the allowlist of known to not be sensitive envvars. Otherwise the value is redacted. (I think there would still be value to a string representation of the SDK components. However that is larger work that could be done separately.) Closes: #1018
Member
Author
|
Here is an example. I have a few |
🔍 Preview links for changed docs |
theletterf
approved these changes
Nov 10, 2025
david-luna
approved these changes
Nov 10, 2025
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
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.
This includes all likely to be relevant envvars in the preamble log
message to help with clarity and debugging. The value of envvars are
included if they are on the allowlist of known to not be sensitive
envvars. Otherwise the value is redacted.
(I think there would still be value to a string representation of the
SDK components. However that is larger work that could be done
separately.)
Closes: #1018