Re: Full Logging Solutions
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 wrote: > On Oct 19, 10:25 am, schapirama 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 > > (schap...@logworm.com) 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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Full Logging Solutions
Jeff, No, your Rails.logger.info is not logged to logworm; you need to use logworm-specific commands to log with us. By default, the logworm gem will automatically log information about each HTTP request that your application receives. If you want to log app-specific information (and you're encouraged to do so), then you need to use the logworm log_in command. BTW, logworm entries are stored in a database as hash-maps, not free-form text, so they can be easily queried. We have built-in mechanisms for daily dumps of your logs to S3 -- contact me if you're interested. The beta account gives you up to 3 logging tables, with 10MB each. That is enough, for example, for ~30K entries recording More complete docs available at: http://www.logworm.com/docs - A -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Deploy failing
I'm getting the following error from an app that I haven't pushed in a few months. I updated to Rails 3.0.1 and tried to deploy and got the following error. I tried going back to 3.0.0, but got the same error again. Any ideas? Thanks, Russell. -> Heroku receiving push -> Rails app detected -> Gemfile detected, running Bundler version 1.0.0 Unresolved dependencies detected; Installing... /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:49:in `initialize': not in gzip format (Zlib::GzipFile::Error) from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:49:in `new' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:49:in `initialize' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_reader.rb:64:in `each' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_reader.rb:55:in `loop' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_reader.rb:55:in `each' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:32:in `initialize' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:17:in `new' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:17:in `open' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package.rb: 58:in `open' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/format.rb: 63:in `from_io' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/format.rb: 51:in `from_file_by_path' from /usr/ruby1.8.7/lib/ruby/1.8/open-uri.rb:32:in `open_uri_original_open' from /usr/ruby1.8.7/lib/ruby/1.8/open-uri.rb:32:in `open' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/format.rb: 50:in `from_file_by_path' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:198:in `cached_specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:196:in `each' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:196:in `cached_specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:195:in `each' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:195:in `cached_specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:157:in `fetch_specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/index.rb:7:in `build' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:155:in `fetch_specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/source.rb:70:in `specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/lazy_specification.rb:48:in `__materialize__' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/spec_set.rb:83:in `materialize' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/spec_set.rb:81:in `map!' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/spec_set.rb:81:in `materialize' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/definition.rb:93:in `specs' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/definition.rb:88:in `resolve_remotely!' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/installer.rb:35:in `run' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/installer.rb:8:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/cli.rb:217:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/vendor/thor/task.rb:22:in `send' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/vendor/thor/task.rb:22:in `run' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/vendor/thor/invocation.rb:118:in `invoke_task' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/vendor/thor.rb:246:in `dispatch' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/ bundler/vendor/thor/base.rb:389:in `start' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/bin/ bundle:13 from /usr/ruby1.8.7/bin/bundle:19:in `load' from /usr/ruby1.8.7/bin/bundle:19 FAILED: http://docs.heroku.com/bundler ! Heroku push rejected, failed to install gems via Bundler -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: What is the expected Sendgrid add-on delay in sending outbound email?
My problem was that my email account was identifying the confirmation emails as spam. Wes On 10/19/10 3:08 PM, Eric Anderson wrote: On Oct 15, 4:50 pm, Wes Gamble wrote: Registered a couple of users on my site and still haven't seen confirmation emails - they appear to have been sent per the logs. What's the longest anyone has had to wait to see emails from their sitees when using the free Sendgrid add-on. Just trying to get a sense of reasonable expectation. They come quick for me. You might want to check to ensure the address did not get blacklisted on Sendgrid. You can find your username/ password by looking at your Heroku environment variables. Then login to the Sendgrid site and look around for the list of addresses blocked. I had a site sending me e-mails when significant events happened. One day the e-mails stopped. I logged into Sendgrid and saw my address was blacklisted. I remove it from the blacklist and the e- mail started flowing again. Just something to check. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: What is the expected Sendgrid add-on delay in sending outbound email?
On Oct 15, 4:50 pm, Wes Gamble wrote: > Registered a couple of users on my site and still haven't seen > confirmation emails - they appear to have been sent per the logs. > > What's the longest anyone has had to wait to see emails from their site > when using the free Sendgrid add-on. > > Just trying to get a sense of reasonable expectation. They come quick for me. You might want to check to ensure the address did not get blacklisted on Sendgrid. You can find your username/ password by looking at your Heroku environment variables. Then login to the Sendgrid site and look around for the list of addresses blocked. I had a site sending me e-mails when significant events happened. One day the e-mails stopped. I logged into Sendgrid and saw my address was blacklisted. I remove it from the blacklist and the e- mail started flowing again. Just something to check. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Full Logging Solutions
On Oct 19, 10:25 am, schapirama 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 > (schap...@logworm.com) 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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Full Logging Solutions
Thanks for the offer I took a look and its not clear 1) whether my existing Rails.logger.info "msg" gets logged to logwworm, or do I need to rewrite 2) can I get a full text download of my log 3) how much history is kept Thanks jeff On Tue, Oct 19, 2010 at 9:25 AM, schapirama wrote: > Eric, Jeff, > > 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 > (schap...@logworm.com) and I'll create accounts for you, > > - Agustin > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Full Logging Solutions
Eric, Jeff, 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 (schap...@logworm.com) and I'll create accounts for you, - Agustin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
