flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brock Noland <br...@cloudera.com>
Subject Re: "Standard" HTTP logging stack? (0.9.3 => 1.2 Upgrade)
Date Thu, 29 Nov 2012 17:19:57 GMT
I would use the Spool Directory source in 1.3 to upload the logs files once
apache rolls the log.

On Wed, Nov 28, 2012 at 6:33 PM, Robert Slifka <robert.slifka@gmail.com>wrote:

> Hi all,
>
> Simple HTTP access.log aggregation case here.  Front ends running Apache
> needing to aggregate/sink all access.log data to S3.
>
> Right now we're on OG 0.9.3:
>
> nginx => access.log => tailSource => Collector => S3
>
>
> For 1.2, I was under the impression we would simplify and move to:
>
> Apache => Syslog => Agent…Agent => S3.
>
>
> However it looks like Apache can only Syslog the error.log.  Am I missing
> something?
>
> What's the recommended 'standard' setup?
>
> Thanks guys,
>
> Rob
>
>


-- 
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Mime
View raw message