Skip to content

Conversation

@bitbeckers
Copy link
Contributor

As we're getting high loads on Sentry spans, we reduce the sampling rate from 1.0 to 0.1 for production and 1.0 on staging.

The reason for this is to primarily lower the amount of traces sent. However, we keep it 100% on staging to detect bugs and as traffic is lower there

Closing #261

As we're getting high loads on Sentry spans, we reduce the sampling rate
from 1.0 to 0.1 for production and 1.0 on staging.

The reason for this is to primarily lower the amount of traces sent.
However, we keep it 100% on staging to detect bugs and as traffic is
lower there
@bitbeckers bitbeckers added the enhancement New feature or request label Mar 11, 2025
@bitbeckers bitbeckers requested a review from Jipperism March 11, 2025 15:20
@bitbeckers bitbeckers self-assigned this Mar 11, 2025
@github-actions
Copy link

Coverage Report

Status Category Percentage Covered / Total
🟢 Lines 26.23% (🎯 26%) 1599 / 6096
🟢 Statements 26.23% (🎯 26%) 1599 / 6096
🟢 Functions 69.23% (🎯 69%) 36 / 52
🟢 Branches 73.85% (🎯 73%) 113 / 153
File CoverageNo changed files found.
Generated in workflow #216 for commit a1654ca by the Vitest Coverage Report Action

@Jipperism Jipperism merged commit 7dbccea into develop Apr 5, 2025
2 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in Hypercerts dev team daily ops Apr 5, 2025
@Jipperism Jipperism linked an issue Apr 5, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Lower Sentry sampling rates

3 participants