Eric, My apologies for not giving you an account earlier --as you said, since we're still in beta we have to manage the number of accounts we give out.
Your questions about the meaning of "beta" are valid. The current setup is fully functional and completely stable. We have approx ~100 live users and are handling tens of transactions per second. The logworm gem, which you install with your application, sends log entries to our servers using a light-weight protocol (not HTTP); the log entries are immediately stored in a queue, and then asynchronously handled by separate workers. From your application point of view, logworm adds just ~1ms. of overhead to the processing of an incoming request. If our workers or our databases go down, your messages will simply accumulate in a queue. We have, indeed, had internal downtimes due to DB migrations, but that was completely hidden from clients and in fact no messages were lost. If, on the other hand, it's the queue itself goes down, then log entries will certainly get lost, and you application will see higher latency as TCP retries the connection to the servers (until it times out). We have a clustered setup of active- active servers (inside the same EC2 zone as Heroku) to make this situation as unlikely as possible. In the 4 months since this setup has been operational, we haven't had a single issue with the queues. The main reason we're limiting the number of beta users is precisely that we want to be able to guarantee good response times whenever there are issues or questions. Now that you have a beta account, you can count on getting prompt responses for us. ;-) I hope this helps. Thanks for trying logworm out! - Agustin On Oct 19, 4:03 pm, Eric Anderson <[email protected]> wrote: > On Oct 19, 10:25 am, schapirama <[email protected]> wrote: > > > I'm currently running a complete logging solution for Heroku, but the > > add-on is still in beta. See: > > http://www.logworm.com > > > If you're interested, please contact me directly > > ([email protected]) and I'll create accounts for you, > > Thanks, I will e-mail you at that address. If you look at my post you > see that I actually mentioned your service is right up my alley. I > tried to signup up with your service a month or so ago (using your > signup form) and never heard a response back. So things I am wondering > are: > > * The "beta" label scares me. How stable is your service? I want good > log data but I don't want to have a unstable app to get it. > Specifically I am wondering what happens if your service goes down. > Does it take my service with it or does it bundle up the message in a > queue and send to you when everything is working again. If it takes > down my service do you have any historical data regarding service up- > time. If you are rock solid I can risk it (after all Heroku is up and > down a few times a month itself) but if you take my service down on a > regular basis obviously that won't work. > * The lack of response on the signup also concerns me. I realize > private beta means that not everybody that wants in can get in. But > once I am in can I count on your service to be responsive should > problems show up? > > Other than that I like the look of your setup and look forward to > working with you. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
