logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bijith Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-789) Where can I view the embedded flume agent startup logs
Date Fri, 22 Aug 2014 17:40:12 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107151#comment-14107151
] 

Bijith Kumar commented on LOG4J2-789:
-------------------------------------

Hi Ralph,
Thanks. I doubt that it is using default log to console because, I don't see any logs in console
either


> Where can I view the embedded flume agent startup logs
> ------------------------------------------------------
>
>                 Key: LOG4J2-789
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-789
>             Project: Log4j 2
>          Issue Type: Question
>          Components: Flume Appender
>    Affects Versions: 2.0-rc2
>            Reporter: Bijith Kumar
>
> Question is about the INFO/ERROR statements logged by the embedded flume agent during
startup.
> When running from eclipse I am able to see these logs in the console. However, when deployed
in Tomcat, the log doesn't appear in application or catalina.out logs. I tried adding the
below configuration in my log4j2.xml but that didn't work either
> <Logger name="org.apache.flume" level="INFO">
> 			<AppenderRef ref="applicationFile" />
> </Logger>
> Just to make it clear, I am talking about the below logs (i.e.the embedded agent startup
logs)
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Processing:agent1
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Processing:agent1
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Processing:agent1
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Processing:agent1
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Processing:agent1
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Added sinks: agent1 Agent: flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0
> 14/08/20 16:37:12 INFO conf.FlumeConfiguration: Post-validation flume configuration contains
configuration for agents: [flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0]
> 14/08/20 16:37:12 INFO node.AbstractConfigurationProvider: Creating channels
> 14/08/20 16:37:12 INFO channel.DefaultChannelFactory: Creating instance of channel channel-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0
type file
> 14/08/20 16:37:12 INFO node.AbstractConfigurationProvider: Created channel channel-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0
> 14/08/20 16:37:12 INFO source.DefaultSourceFactory: Creating instance of source source-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0,
type org.apache.flume.agent.embedded.EmbeddedSource
> 14/08/20 16:37:12 INFO sink.DefaultSinkFactory: Creating instance of sink: agent1, type:
avro
> 14/08/20 16:37:12 INFO sink.AbstractRpcSink: Connection reset is set to 0. Will not reset
connection to next hop
> 14/08/20 16:37:12 INFO node.AbstractConfigurationProvider: Channel channel-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0
connected to [source-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0, agent1]
> 14/08/20 16:37:12 INFO file.FileChannel: Starting FileChannel channel-flumeAppender-fa1d7b7179c6a671efca3ac5c658c6c0
{ dataDirs: [flumedata/file-channel/data] }...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message