Skip to content
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

maxStackTraceLines="0" is not honored #522

Closed
nr-ahemsath opened this issue Apr 7, 2021 · 0 comments · Fixed by #523
Closed

maxStackTraceLines="0" is not honored #522

nr-ahemsath opened this issue Apr 7, 2021 · 0 comments · Fixed by #523
Assignees
Labels
bug Something isn't working

Comments

@nr-ahemsath
Copy link
Member

nr-ahemsath commented Apr 7, 2021

The maxStackTraceLines configuration value (https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-configuration/#config-maxStackTraceLines) is not honored if the value is set to "0".

Expected behavior: no stack trace lines will be sent.
Actual behavior: all available stack trace lines are sent.

Our support team brought this to our attention; a customer wants to configure the agent to keep sending error trace data to New Relic, but without any stack trace information included. Upon investigation, we found that setting maxStackTraceLines to 0 had no effect on the number of stack trace lines sent due to a flaw in the logic for handling this config value. This will be fixed in a PR shortly.

@nr-ahemsath nr-ahemsath added the bug Something isn't working label Apr 7, 2021
@nr-ahemsath nr-ahemsath changed the title maxStackTraceLines="0 maxStackTraceLines="0" is not honored Apr 7, 2021
@nr-ahemsath nr-ahemsath self-assigned this Apr 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant