-
Notifications
You must be signed in to change notification settings - Fork 3
Changing deprecated raven library to sentry-sdk library #30
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
base: stable/2024.1-m3
Are you sure you want to change the base?
Conversation
|
How could we test if the Image would work? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…h wrong SENTRY_DSN format
…tests - Added SentryFilterEngine for filtering Sentry events based on configurable rules. - Introduced RuleValidationError for handling rule validation errors. - Created load_rules_from_file function to load and validate rules from YAML configuration. - Developed unit tests for SentryFilterEngine and rule loader to ensure functionality and validation. - Updated Sentry WSGI middleware to integrate filtering engine and handle environment configurations. - Added example YAML configuration for Sentry filtering rules. - Updated requirements to use the latest version of sentry-sdk.
4cfdde2 to
e6451a2
Compare
|
I thought about the Problem more and came to the conclusion that SENTRY_EXCLUSIONS_LIST is not robust enough to handle different filter cases. Also there requirements came to my mind:
the new implementation features a FilterEngine for Sentry. this currently is based on the latest version of sentry-sdk and needs a new Sentry Deployment (23.6) to function correctly. |
Sentry-sdk library can replace the deprecated raven library.
There is the option to use a Flask Integration or use the WSGI Integration.
The WSGI Integration is less intrusive.
To provide the necessary filtering a callback function can be declared that receives the exception event before it gets send to Sentry. here we can filter over a list of exception names that should be ignored.
env vars that should be provided:
SENTRY_EXCLUSIONS_LIST are the comma separated exception names.