[
https://issues.apache.org/jira/browse/CHUKWA-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated CHUKWA-530:
-----------------------------
Resolution: Fixed
Fix Version/s: 0.5.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Thanks Ari, I just committed this.
> Syslog Adaptor for mapping Syslog facility name to Chukwa data type
> -------------------------------------------------------------------
>
> Key: CHUKWA-530
> URL: https://issues.apache.org/jira/browse/CHUKWA-530
> Project: Chukwa
> Issue Type: New Feature
> Components: data collection
> Environment: Java 6, Mac OS X
> Reporter: Eric Yang
> Assignee: Eric Yang
> Fix For: 0.5.0
>
> Attachments: CHUKWA-530-draft.patch, CHUKWA-530.patch
>
>
> UDPAdaptor can record syslog logs but the log entry is tagged with Chukwa
> internal data type at adaptor start up time. I am thinking to extend
> UDPAdaptor to record syslog messages with small enhancements. SyslogAdaptor
> can extract facility name field from syslog message to tag facility name as
> the data type. This would provide the ability to invoke different demux
> parsers base on the facility name in syslog. HOSTNAME can also be mapped to
> source for Chukwa chunk meta data.
> My use case is to configure hadoop log4j.properties to log everything through
> org.apache.log4j.net.SyslogAppender to one SysLogAdaptor on the local Chukwa
> agent, and invokes different parsers for audit log and name node log.
> Facility name is some what limited, but it should be enough type left to
> manage hadoop log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
