使用 Splunk 监控 Amazon S3 日志？

Question

We have a large extended network of users that we track using badges. The total traffic is in the neighborhood of 60 Million impressions a month. We are currently considering switching from a fairly slow, database-based logging solution (custom-built on PHP—messy...) to a simple log-based alternative that relies on Amazon S3 logs and Splunk.

After using Splunk for some other analyisis tasks, I really like it. But it's not clear how to set up a source like S3 with the system. It seems that remote sources require the Universal Forwarder installed, which is not an option there.

Any ideas on this?

Answer 1

Very late answer but I was looking for the same thing and found a Splunk app that does what you want, http://apps.splunk.com/app/1137/ . I have yet not tried it though.

Answer 2

I would suggest logging j-son preprocessed data to a documentdb database. For example, using azure queues or simmilar service bus messaging technologies that fit your scenario in combination with azure documentdb. So I'll keep your database based approach and modify it to be a schemaless easy to scale document based DB.

Answer 3

I use http://www.insight4storage.com/ from AWS Marketplace to track my AWS S3 storage usage totals by prefix, bucket or storage class over time; plus it shows me the previous versions storage by prefix and per bucket. It has a setting to save the S3 data as splunk format logs that might work for your use case, in addition to its UI and webservice API.

Answer 4

You use Splunk Add-On for AWS .

This is what I understand,

1. Create a Splunk instance. Use the website version or the on-premise AMI of splunk to create an EC2 where splunk is running.

2. Install Splunk Add-On for AWS application on the EC2.

3. Based on the input logs type (eg Cloudtrail logs, Config logs, generic logs, etc) configure the Add-On and supply AWS account id or IAM Role, etc parameters.

4. The Add-On will automatically ping AWS S3 source and fetch the latest logs after specified amount of time (default to 30 seconds).

For generic use case (like ours), you can try and configure Generic S3 input for Splunk