-
Notifications
You must be signed in to change notification settings - Fork 1
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
How to prevent deprecations submitted to sentry #12
Comments
@skrollme |
In the project where we had the most problems with this, sentry was removed (in favor of NewRelic) in the meantime, so - no, real solution here, @eliasws . |
Thanks for answering anyway! |
Any news on this @heyjorgedev ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
... as the title states it is not a problem but more of a question how to configure the extension properly:
Whilst testing this sentry-integration we see, that lots of deprecations are submitted to sentry which a) eat sentry-quota and b) eat performance due to unnecessary network connections.
It seems that even if the system is configured to ignore E_USER_DEPRECATED these are once ignored in a first run, then - because unhandled - escalate to a real EXCEPTION and then get picked up by the sentry-logic and are submitted sentry.
Do you have any best-practises avoiding this behavior?
The text was updated successfully, but these errors were encountered: