Beeline prevents sentry.io from reporting about beeline-python

[fitzoh]

Disregard, I'm dumb.

So I think honeycomb was killing sentry reporting, but it was because I missed the gevent monkeypatch warnings and was itself blowing up due to RecursionErrors.

Fixing the monkeypatching issue seems to get everything working.

[danyelf]

Thanks for the followup! Glad you caught it.

[tredman]

Hey, thanks for the report. I am looking into this. I am not aware of any obvious places these libraries would conflict so I will need to spend some time reproducing the problem. We're sentry customers as well so I should be able to test this out.

When you say you removed Honeycomb and Sentry worked again, did you just remove the call to beeline.init or did you remove the middleware setting (below) in your django settings.py? Or both?

MIDDLEWARE = [
    ...
    'beeline.middleware.django.HoneyMiddleware',
    ...
]

[tredman]

I tried to reproduce this locally with the beeline, sentry SDK, django, and gunicorn versions above. I was able to see instrumentation in Honeycomb, and when I generated an ISE with an unhandled exception (raise Exception("foo") at an arbitrary point in the code, the error event made it to Sentry. When you refer to automatic error reporting, is there a specific type of error that isn't getting through? Could be that I am just testing the wrong thing.