This repository has been archived by the owner on Oct 18, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
requestLog is not being sent #19
Comments
Hi, I can confirm that there is a NPE in that case. Note that it's not because Note that dropwizard-gelf comes with its own request logger ( environment.servlets()
.addFilter("request-logs", new GelfLoggingFilter())
.addMappingForUrlPatterns(EnumSet.allOf(DispatcherType.class), true, "/*"); |
Debugging trying to figure out why my http requests aren't showing up in my logging server I found that the ch.qos.logback.core.AppenderBase is throwing a ClassCastException.
So it appears that thad the RequestLog is sending an AccessEvent but the underlying logging structure can't handle that. |
@kevinmic Which version of Dropwizard are you using? |
io.dropwizard:dropwizard-core:jar:1.0.0 |
I'm seeing the same issue. Dropwizard v1.1.2. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I am trying to also send the requestLog to our graylog server. Unfortunately, it does not work (messages are dropped silently). The instance is created correctly but messages cause a NPE in LogbackLogEvent.getCalleeStackTraceElement:74 since the callerDataArray in LogbackLogEvent.loggingEvent.getCallerData() is null.
My entries in the config section:
Versions: Dropwizard 0.9.2, Dropwizard-GELF 0.9.2-4
The text was updated successfully, but these errors were encountered: