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

Updates sentry-sdk (0.7.7->0.19.5) and introduces traces_sample_rate #8343

Merged
merged 1 commit into from
Feb 3, 2021

Conversation

gdixon
Copy link
Contributor

@gdixon gdixon commented Feb 2, 2021

Description

Updates the sentry-sdk version and introduces traces_sample_rate (set to sample 35% of requests).

Refers/Fixes

Refers: #8309

Testing

@octavioamu provided figures on reqs/min to get us to the 0.35 figure. If the load changes, we might need to readdress how much sampling we do.

@gdixon gdixon linked an issue Feb 3, 2021 that may be closed by this pull request
@thelostone-mc
Copy link
Member

yo @octavioamu mind dropping the reasons why we set value as 0.35 -> just so folks can refer this PR later if needed

@thelostone-mc thelostone-mc merged commit 4dcf9ce into gitcoinco:master Feb 3, 2021
@gdixon
Copy link
Contributor Author

gdixon commented Feb 3, 2021

yo @octavioamu mind dropping the reasons why we set value as 0.35 -> just so folks can refer this PR later if needed

@thelostone-mc - theres ~700 reqs/min and the example given in the docs (https://docs.sentry.io/product/performance/distributed-tracing/) is aiming for around ~250/min, (700 * 0.35 will give us ~245).

If this looks like too few or too many samples in practice we can ratchet up or down once we see the data coming into sentry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Sentry Python SDK
2 participants