Getting lockdown with sentry-java and log4j 2.x

I’ve just upgraded from the raven library and having some problems getting logging working in production. Some logs get through but I was getting a lot of errors - I suspect a loop - where a sentry error was being logged back to the Sentry servers which eventually created an overload of errors in the time period.

My log4j2.xml contains…


on the console I see

SP WARN 09:42 AbstractConnection:93 - An exception due to the connection occurred, a lockdown will be initiated.
io.sentry.connection.ConnectionException: {“error”:“Event dropped due to filter”}
at io.sentry.connection.HttpConnection.doSend( ~[sentry-1.5.2.jar:?]
at io.sentry.connection.AbstractConnection.send( [sentry-1.5.2.jar:?]
at io.sentry.connection.BufferedConnection.send( [sentry-1.5.2.jar:?]
at io.sentry.connection.BufferedConnection$ [sentry-1.5.2.jar:?]
at java.util.concurrent.Executors$ [?:1.7.0_151]
at java.util.concurrent.FutureTask.runAndReset( [?:1.7.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( [?:1.7.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ [?:1.7.0_151]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.7.0_151]
at java.util.concurrent.ThreadPoolExecutor$ [?:1.7.0_151]
at [?:1.7.0_151]
Caused by: Server returned HTTP response code: 403 for URL:
at ~[?:1.7.0_151]
at ~[?:1.7.0_151]
at io.sentry.connection.HttpConnection.doSend( ~[sentry-1.5.2.jar:?]
… 10 more

How do I see that the “filter” is which is dropping the event?

(For what it’s worth, we’ve been discussing this over support.)

For other viewers: you can adjust inbound filters at$ORG/$PROJECT/settings/filters/