-
Notifications
You must be signed in to change notification settings - Fork 34
[Part 2] feat: Implement Span stack trace specification #827
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
Conversation
- INSTANA_CONFIG_PATH - in-code config - agent config Signed-off-by: Varsha GS <varsha.gs@ibm.com>
…errides Signed-off-by: Varsha GS <varsha.gs@ibm.com>
Signed-off-by: Varsha GS <varsha.gs@ibm.com>
bad6b7b to
929a7df
Compare
Signed-off-by: Varsha GS <varsha.gs@ibm.com>
b82a852 to
c5bfe08
Compare
pvital
left a comment
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.
Just three recommendations.
…d stack trace Signed-off-by: Varsha GS <varsha.gs@ibm.com>
30d6590 to
7b77f0b
Compare
|
pvital
left a comment
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.
It looks good to me.



What's there in this PR?
Added stack-trace support for all configuration sources in the following precedence:
Runtime Stack Trace Collection Flow:
Note
We support technology-specific overrides (for all
EXITspans!) for all the mapping based config sources (YAML, in-code and Agent)