Open Prillan opened 5 years ago
To solve your intermediate problem, you can use ignore_logger
: https://docs.sentry.io/platforms/python/logging/#ignoring-a-logger
Not sure what's best to do about the more general bug yet. Thanks for raising it though!
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
This is probably a bug that is worth looking into. Putting it in the internal backlog at low priority
Note: might be easier to fix once we have lifecycle hooks.
Can anybody provide a solution?
Same here, Sentry is dropping my exceptions.
Exception: Test Exception
[sentry] INFO: event processor (<function DedupeIntegration.setup_once.
Hey @thianesh, one thing you can do is disable the DedupeIntegration
(see docs), though that can of course lead to, well, duplicates in other parts of the system.
Could you give us a bit more info on where you're seeing this? Do you also have a before_send
like the OP describes in the first comment?
The dedupe integration drops events that were never sent before.
Ideally, dedupe would run after
before_send
or there should be a possibility to hook into the event processing earlier. A third option would be to bring back the option to ignore specific loggers from raven.Example code:
Output from the flask server: