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

chore(config): adjust Sentry sample rate to more conservative level #412

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

bkrem
Copy link
Member

@bkrem bkrem commented Jan 18, 2024

Description

Type of change

Please put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

@bkrem bkrem requested a review from devceline January 18, 2024 09:27
Copy link

vercel bot commented Jan 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
app-web3inbox ✅ Ready (Inspect) Visit Preview Jan 18, 2024 9:27am

@bkrem bkrem requested a review from enesozturk January 18, 2024 09:27
Copy link
Collaborator

@devceline devceline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bkrem bkrem merged commit 16e37f3 into main Jan 18, 2024
3 checks passed
@bkrem bkrem deleted the chore/adjust-sentry-sample-rate branch January 18, 2024 09:29
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.

3 participants