No Reports for 6/11/2009
You'll probably notice that most buckets are showing zero traffic for 6/11/2009. This is due to a stoppage of log delivery at Amazon (thus meaning we had no data to build reports from). This was at Amazon's side, and thus out of our control, though technically we did have something to do with it.We've been working with the Amazon folks to track down a data integrity issue in the logs. In response to our request (linked below), Amazon mentioned that they'd stopped logging temporarily while they were looking into the issue:http://developer.amazonwebservices.com/connect/thread.jspa?threadID=32849Apparently, by that they meant that they had suspended log delivery ENTIRELY, across all of S3. As a result, no logfiles made it to anybody's bucket on the 11th, so you'll see a hole in your reports.Amazon is currently fielding a flood of questions about this, so I figured it would be a good idea to give you all a heads up here.Logs are showing up for the 12th, so your stats should spring back to life tomorrow.
jason
Friday, June 12, 2009
We're seeing some really bizarre logs from June 4, June 5 and June 6.See the graph here:
http://files.na.mcneel.com/stats.PNGThe Pages/Files/Hits and Sites/Visits graphs look normal; the KBytes graph has a spike of 32,630,684,503 KBytes. A fairly ordinary daily maximum for us is 150,000,000 KBytes - being off by a couple orders of magnitude is pretty bizarre.Do you think this is an example of the corruption that you mentioned in this post?
[ reply to this topic ]
[ return to topic list ]
|