Fix #54 - adding a configuration to log full stack trace in error.stack #78
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.
Include full exception stack trace
Only supported on logback
You can configure the logging extension to include in
error.stackthe full stack trace just like the downstream library does.This includes the caused by chain.
As an example, this snippet:
Will set the
error.stackasDefault is
falsefor retro-compatibility.This setting can be enabled via environment variable (
NEW_RELIC_LOG_EXTENSION_INCLUDE_FULL_ERROR_STACK=true) or system variable (-Dnewrelic.log_extension.include_full_error_stack=true).Be aware that enabling this setting will use the downstream library's stacktrace generation, not taking in consideration
the value of Exception Stack Trace Size.