Skip to content

docs(tracer): additional scenario when to disable auto-capture #499

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

Merged
merged 1 commit into from
Jul 2, 2021

Conversation

heitorlessa
Copy link
Contributor

@heitorlessa heitorlessa commented Jul 2, 2021

Issue #, if available: #476

Description of changes:

This PR adds an additional scenario on when to disable auto-capture response - >64K responses

Checklist

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@boring-cyborg boring-cyborg bot added the documentation Improvements or additions to documentation label Jul 2, 2021
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 2, 2021
@heitorlessa heitorlessa added area/tracer and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 2, 2021
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 2, 2021
@heitorlessa heitorlessa merged commit 7c88d11 into develop Jul 2, 2021
@heitorlessa heitorlessa deleted the docs/tracer-response-limit branch July 2, 2021 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant