Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sentry doesn't pick up errors via Slack Webhook

See original GitHub issue

I’m using Django and when I cURL my endpoint, the exception is raised and logged in Sentry successfully. However, when Slack hits the endpoint through its webhook system, it somehow doesn’t get logged in Sentry. I know it’s still being hit because the 500 response still shows up in my logs and the error gets logged correctly in rollbar.

Here’s the code:

@csrf_exempt
def Slack_Webhook(request):

  data = json.loads(request.body)

  raise Exception()

Issue Analytics

State:
Created 4 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

untitakercommented, Apr 7, 2019

Ah! Go to your project settings, go to “Inbound Filters”. There you will see the option for “known web-crawlers” likely enabled:

We maintain a regex for those user agents here: https://github.com/getsentry/sentry/blob/e6cc8483b3992fb02ebb39649efd2b264fcadeca/src/sentry/filters/web_crawlers.py#L38-L39

If you want to refine that regex somehow feel free to open a PR.

I will close this though since it’s not a bug in the SDK. Thanks for responding so quickly!

0reactions

reparadocscommented, Apr 7, 2019

Once I upgraded, I now get this error:

Apr 06 21:27:07 trestle-shrine app/web.1:  [sentry] ERROR: Unexpected status code: 403 (body: b'{"error":"Event dropped due to filter: web-crawlers"}') 
Apr 06 21:27:07 trestle-shrine app/web.1: ERROR:sentry_sdk.errors:Unexpected status code: 403 (body: b'{"error":"Event dropped due to filter: web-crawlers"}')

Is the slack webhook being miscategorized as a web crawler? Is there a way to disable this filter?.