Open stevenmck97 opened 6 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-issues for triage ⏲️
@stevenmck97, Thanks for reaching out and providing detailed information about the issue you're facing with the 'Large Render Blocking Asset' info event in Sentry. We understand the importance of managing your quota efficiently, and we're here to assist you.
To investigate this matter further and provide you with the most accurate and tailored support, we kindly request that you reach out to our support team directly via email. Please send your inquiry to support@sentry.io and include as much detail as possible.
Environment
SaaS (https://sentry.io/)
What are you trying to accomplish?
Version info:
We are trying to filter out the 'Large Render Blocking Asset' info event from being sent to Sentry.
How are you getting stuck?
The 'Large Render Blocking Asset' info log began appearing in our Sentry log after an update from from version 7.59.0 to 7.77.0. Using the
CaptureConsole
from the integrations package, we set the level to "error" so as to only have error events sent through to Sentry. Despite this, the log was still showing up in Sentry and using up replays. We then implemented thebeforeSend
hook as another precaution to only send error events.The info event is still being logged in Sentry. I'm hoping for some support as to how we can filter this out to prevent it using our quota. This project is currently in maintenance mode with no active development and we don't currently have capacity to look into the info event itself. Any assistance would be appreciated.
Where in the product are you?
Issues
Link
No response
DSN
No response
Version
No response