Filtered events logged at error level

[ipmb]

{
    "asctime": "2018-05-17 11:58:33,097",
    "created": 1526572713.097566,
    "levelname": "ERROR",
    "levelno": 40,
    "filename": "base.py",
    "funcName": "_failed_send",
    "lineno": 679,
    "module": "base",
    "message": "Sentry responded with an API error: APIError(Event dropped due to filter: web-crawlers)",
    "name": "sentry.errors",
    "pathname": "/srv/proj/local/lib/python2.7/site-packages/raven/base.py",
    "process": 11799,
    "processName": "MainProcess"
}

I have my application configured to capture all error logs and this one tends to be particularly noisy. Filtering events seems like standard operation and could be logged at INFO instead of ERROR which it doesn't appear to be.

[LadyNamedLaura]

@ashwoods any news on this? I'm still not sure whether this should be fixed in raven or sentry itself (see getsentry/sentry#8763 ) but I would really like to see this fixed.