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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load OTel SDK config from environment variables and system properties.… #1434
Load OTel SDK config from environment variables and system properties.… #1434
Changes from 6 commits
ee61c7b
ecb469b
a89bd63
cc3490c
139c096
6846a02
e3316a5
45f8efe
4f75414
70eef3a
f5c4825
e5cb582
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a bit better to not rely on global state (here in system properties) as we have to take care of the cleanup here.
What I think could be slightly better is to add an argument to the
OpenTelemetrySdkService
constructor to control which system properties are present or not if we can. While this slightly alters the design for test purpose it could be worth it here as it allows to get rid of any early cleanup or finally block. Also with such a change there can't be any side effect if system properties are set on the JVM that execute the tests which usually require us to ensure properties are not set in some cases.The
AutoConfiguredOpenTelemetrySdkBuilder.setConfigPropertiesCustomizer
allows to override the config properties, but it's package-private so usingAutoConfigureUtil.setConfigPropertiesCustomizer
is needed. While it's an internal API doing this only for tests should be fine.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we postpone this improvement? I lack time to clean this up unfortunately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can definitely postpone that to later improvement. Just to keep it safe once this test class has executed adding an
@AfterAll
method to ensure there are no side effects on things that execute after.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great suggestion. Please review below.