-
Notifications
You must be signed in to change notification settings - Fork 127
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
add span stacktrace config option #1414
Merged
trask
merged 16 commits into
open-telemetry:main
from
SylvainJuge:span-stacktrace-config
Sep 16, 2024
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
1945184
define config constants
SylvainJuge b2a4031
clarify opt-out and disabling
SylvainJuge 0d2b8c9
markdown lint
SylvainJuge 0d61423
config option can support multiple units
SylvainJuge d097463
provide a way to enable for all spans
SylvainJuge 22d0a9e
Apply suggestions from code review
SylvainJuge 887efdf
Update span-stacktrace/README.md
SylvainJuge b56d549
Update span-stacktrace/README.md
SylvainJuge d8c39e8
easier usage with autoconfig spi + fix tests
SylvainJuge dc0937b
update readme with new config API
SylvainJuge a965bff
reformat
SylvainJuge aefb684
update readme
SylvainJuge 4727a24
make constants private
SylvainJuge 6b66fe7
Update span-stacktrace/README.md
SylvainJuge 3488bd3
update config option as discussed in SIG meeting
SylvainJuge e7a8cb0
thou shall lint!
SylvainJuge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
The delimiter situation is always a bit hard.. Thoughts:
-
into.
, so there doesn't seem to be any point in introducing other delimeters.otel.java.experimental.stacktrace.*
(orotel.java.experimental.stacktraceprocessor.*
) would allow for a more uniform property schema. But on the other hand, the component is currently named*-span-stacktrace
- maybe the component name is worth revisiting?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'm fine to remove
-
and replace it with.
, for now we just need to have one configuration option to start, we will of course need to revise this later when making this feature stable.I think the suggestion to use
-
in the feature name came from what we currently have forotel.java.experimental.span-attributes.copy-from-baggage.include
in the baggage-processor, which by the way isn't really consistent as we haveotel.java.experimental.span-attributes
as prefix for a module namedbaggage-processor
.As long as things are not marked as stable, I think those minor inconsistencies are fine and acceptable, especially in the contrib repo where things are mostly alpha.
However we probably need to have some proper definition somewhere about those configuration options, for example to at least define what are the main namespaces like
otel.java.*
,otel.javaagent.*
orotel.java.experimental.*
or even define a global registry with all the possible options to ensure there isn't any conflict between all the repositories. Also, this might be something also happening in other platforms & otel components SIGs.However that's definitely something that will take a while and should be covered separately, and I know that it sounds like "let's start another SIG about configuration options" 😄 .
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.
Ha - well unfortunately I doubt we'll get any additional clarity around property naming anytime soon. There's already a dedicated config sig (which I lead), focussing on building out declarative configuration which aims to replace the system property / env var config scheme as the dominant mechanism for configuration. That's where all the configuration effort is being spent these days.
I think you're right to stick with precedents that already exist in this repo - I wasn't aware of those.
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.
Ok, then let's stick to
otel.java.experimental.span-stacktrace.min.duration
for now if you agree and we can always change it later as it's experimental, we can even still support the current experimental config for as long as we'd like.