StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow reliable are amazon s3 access log files?
text
Body
copied!<p>We're moving to s3 to start serving some of the statically generated content for our web app. We have been looking at a mechanism for building a metric system about the usage of our site and we were planning on parsing the access logs for S3 by passing additional information to be logged on the content GET requests. We happened across the following <a href="http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?LogDelivery.html" rel="noreferrer">entry in the developers guide</a>:</p> <blockquote> <p>Best Effort Server Log Delivery</p> <p>The server access logging feature is designed for best effort. You can expect that most requests against a bucket that is properly configured for logging will result in a delivered log record, and that most log records will be delivered within a few hours of the time that they were recorded.</p> <p>However, the server logging feature is offered on a best-effort basis. The completeness and timeliness of server logging is not guaranteed. The log record for a particular request might be delivered long after the request was actually processed, or it might not be delivered at all. The purpose of server logs is to give the bucket owner an idea of the nature of traffic against his or her bucket. It is not meant to be a complete accounting of all requests.</p> </blockquote> <p>We are wondering what other people have experienced with respect to the delivery of access logs? Our alternative is to build an HTTP server and try to meter the metrics ourselves with a different call, but we think that parsing the log files could prove to be less work. We'd like to know if people have seen situations where delivery didn't take place to try to gauge about how accurate we could hope to be because some of the metrics we gather are used in some of our business processes.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload