Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # user >> Syslog Infrastructure with Flume

Copy link to this message
Re: Syslog Infrastructure with Flume

I am not a Hive/HCatalog pro, but I am just wondering why an HCatalog sink, rather than a Hive Sink? Hive is definitely very popular and would be well appreciated if we could get a Hive Sink written. Since HCatalog is supposed to be compatible with the Hive metastore (right?), why not just implement a Hive sink and make it available to a larger community? I'd definitely like to see a Hive Sink, and would definitely prioritize that and then if explicitly required, add HCatalog support to that - this way it is useful to people who use Hive as well. In fact, there already is a Hive Sink jira here:https://issues.apache.org/jira/browse/FLUME-1008.

I am a +1 for a Hive Sink, so please take a look.
Hari Shreedharan
On Monday, October 29, 2012 at 4:37 PM, Roshan Naik wrote:

> I am in the process of investigating the possibility of creating  a HCatalog sink for Flume which should be able to handle such use cases. For your use case it could be thought of as a Hive sink. Goal is basically as follows... it would allow multiple flume agents to pump logs into a hive tables. That would make the data query-able without additional manual steps. Data will get added periodically in the form of new partitions to Hive. You would not have to deal with temporary files or manual addition of data into hive.  
> -roshan
> On Sun, Oct 28, 2012 at 5:45 PM, Ralph Goers <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > Since you ask...
> >
> > In our environment our primary concern is audit logs - have have to audit banking transactions as well as changes administrators make. We have a legacy system that needed to be integrated that had records in a form different than what we want stored. We also need to allow administrators to view events as close to real time as possible. Plus we have to aggregate data across 2 data centers. Although we are currently not including web server access logs we plan to integrate them in over time.  We also have requirements from our security team to pass events for their use to ArcSight.
> >
> > 1. We have a "log extractor" that receives legacy events as they occur and converts them into our new format and passes them to Flume. All new applications use the Log4j 2 Flume Appender to get data to Flume.
> > 2. Flume passes the data to ArcSight for our security team's use.
> > 3. We wrote a Flume to Cassandra Sink.
> > 4. We wrote our own REST query services to retrieve the data from Cassandra.
> > 5. Since we are using DataStax Enterprise version of Cassandra we have also set up "Analytic" nodes that run Hadoop on top of Cassandra. This allows the data to be accessed via normal Hadoop tools for data analytics.
> > 6. We have written our own reporting UI component in our Administrative Platform to allow administrators to view activities in real time or to schedule background data collection so users can post process the data on their own.
> >
> > We do not have anything to allow an admin to "tail" the log but it wouldn't be hard at all to write an application to accept Flume events via Avro and display the last "n" events as they arrive.
> >
> > One thing I should point out. We format our events in accordance with RFC 5424 and store that in the Flume event body. We then store all our individual pieces of audit event data in Flume headers fields.  The RFC 5424 message is what we send to ArcSight. The event fields and the compressed body are all stored in individual columns in Cassandra.
> >
> > Ralph
> >
> >
> > On Oct 26, 2012, at 2:06 PM, Ron Thielen wrote:
> > > I am exactly where you are with this, except for the problem of my not having had time to write a serializer to address the Hostname Timestamp issue.  Questions about the use of Flume in this manner seem to recur on a regular basis, so it seems a common use case.
> > >  
> > > Sorry I cannot offer a solution since I am in your shoes at the moment, unfortunately looking at storing logs twice.