fix: disable tracing across the board #445
Merged
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.
We currently can't use Sentry's tracing functionality because we overrun our tracing data quota within hours. I'm disabling all tracing and plan on re-enabling it across the board once I've worked out how to use it for the debugging tasks I have on my plate right now.
Note that this does not disable error reporting - that's a separate configuration option and this just disables tracing:
https://docs.sentry.io/platforms/javascript/tracing/
My end goal for this is to have tracing configured at a reasonable percentage for each lambda - most will probably end up around 0.1 but some higher volume functions may need even lower settings.