enabling debug logging

1,683 views
Skip to first unread message

Nicholas McKoy

unread,
Sep 11, 2015, 10:07:55 AM9/11/15
to Druid User
Hi, 

Quick question.

Using a realtime node and kafka 8 firehose to ingest a ton of events. seems like all of them are unparseable and im not sure why? i get this error:

ERROR [MonitorScheduler-0] io.druid.segment.realtime.RealtimeMetricsMonitor - [54,704] Unparseable events! Turn on debug logging to see exception stack trace.

I have these lines in my realtimes runtime.properties:
druid.monitoring.monitors=["io.druid.segment.realtime.RealtimeMetricsMonitor"] 

druid.emitter=logging

druid.emitter.logging.logLevel=info


I do see logs but I am not able to see the exception from this error. How can i enable logging to see this exception?

Thanks,

Nicholas McKoy

unread,
Sep 14, 2015, 10:26:11 AM9/14/15
to Druid User
anyone?

charles.allen

unread,
Sep 14, 2015, 11:13:00 AM9/14/15
to Druid User
You'll want to specify a log4j2.xml. There's one in the druid repository for debugging on EVERYTHING in druid, you may want to change the name="io.druid" to name="io.druid.segment.realtime" if the log is too chatty and you're using the realtime node.

Himanshu

unread,
Sep 14, 2015, 11:59:03 AM9/14/15
to Druid User

--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/8c9de327-1841-4c85-ac36-a6808f0a2217%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Nicholas McKoy

unread,
Sep 14, 2015, 2:56:00 PM9/14/15
to Druid User
Charles' suggestion is what worked for me. Thanks guys.

Mark Shannon

unread,
May 31, 2018, 10:37:11 AM5/31/18
to Druid User
How exactly do you do this?


On Monday, September 14, 2015 at 11:13:00 AM UTC-4, charles.allen wrote:

Gian Merlino

unread,
Jun 8, 2018, 12:03:23 AM6/8/18
to druid...@googlegroups.com
Hi Mark,

You can edit the log4j2.xml that is bundled in conf/_common/.

Gian

--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.

To post to this group, send email to druid...@googlegroups.com.

Umar M-Hamid

unread,
Sep 20, 2019, 6:36:22 AM9/20/19
to Druid User
Hi charles! I search log4j2.xml and found it under _common/ but could not find property "name=io.druid" except 

<Configuration status="WARN">
    <Appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout pattern="%d{ISO8601} %p [%t] %c - %m%n"/>
        </Console>
    </Appenders>
    <Loggers>
        <Root level="info">
            <AppenderRef ref="Console"/>
        </Root>
    </Loggers>
</Configuration>

dont know how to resolve my problem

Daniel Hopins

unread,
Sep 20, 2019, 10:17:21 AM9/20/19
to Druid User
  1. You would need to add an entry to the file:
  2. <Logger name="io.druid" level="trace">
  3. <AppenderRef ref="Console"/>
  4. </Logger>
Giving u file that looks like: (for level you can use trace,info,debug,warn)

<Configuration status="WARN">
    <Appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout pattern="%d{ISO8601} %p [%t] %c - %m%n"/>
        </Console>
    </Appenders>
    <Loggers>
  1. <Logger name="io.druid" level="debug">
  2. <AppenderRef ref="Console"/>
  3. </Logger>

        <Root level="info">
            <AppenderRef ref="Console"/>
        </Root>
    </Loggers>
</Configuration>

Reply all
Reply to author
Forward
0 new messages