whenever I embed a Cloudflare Stream video on my website.
I’m not using Sentry in my own code and have no control over these requests, but the error persists and clutters the console for all visitors.
This is frustrating because:
The error is visible to all users who open the console, including clients and developers.
It makes debugging more difficult, especially when looking for real site issues.
There’s currently no option in the Cloudflare dashboard or Stream API to disable or silence these internal Sentry requests.
Please consider:
Providing an option to disable Sentry tracking/scripts for end users, or
Ensuring that these errors are properly handled and not exposed to the browser console.
This would greatly improve the developer experience and avoid confusion for users who are not using Sentry themselves.