Setup question (possible to use existing log data bucket?)
I am completely new to the service, and setting it up it is asking me the bucket name, which is as expected. However, it is also proposing some other directories and locations which are grayed-out, including a subdirectory in the bucked which is described as "your log files will be sent to".What does this mean, that your service will change the log destination that is already set up on a bucket? The wording does not clarify whether this is the case (and which I wouldn't want), or if instead these are some processed files. I do not want to change the existing log destination, which is a single bucket reserved for all logs from all other buckets. And I would expect S3Stat to be able to see where the logs from a bucket go, and pick them up accordingly and automatically. Only this doesn't seem to be the case, from what I see in the grayed out fields.Thanks if you can clarify.
Saturday, November 1, 2008
Sorry for the confusion. You're right that the wording on that page could use some work.As of today, S3stat will only process logfiles living in bucketname/log, and it will deliver stats to bucketname/stats. We initially offered the ability to change those paths, but for silly technical reasons we had to tighten things down a bit. You're right in assuming that we aught to be sniffing this out automatically though. It's on the todo list.In response to your question, no, we won't change the delivery path on your bucket if it's already set up for logging. If you've done the setup yourself, and you'd still like to use S3stat to handle reporting, you'll need to change the delivery path at your end.Anyway, I hope this clears things up a bit. Sorry that we don't quite map to your expectations. Let me know if you have any further questions, and I'll be sure to keep you posted if we end up making those path names more flexible.
Monday, November 3, 2008
[ reply to this topic ]
[ return to topic list ]