Hi Greg My approach with Monit and sessions was to create a specific controller & action to poll, and turn sessions off for it.
http://pastie.textmate.org/188359 It does feel like overkill, mind you, and I'm a little surprised that calling a static file (which is a more elegant solution) creates a session. -- Pat e: [EMAIL PROTECTED] || m: 0413 273 337 w: http://freelancing-gods.com || p: 03 9386 0928 discworld: http://ausdwcon.org || skype: patallan On 29/04/2008, at 4:23 AM, Greg Willits wrote: > > One of the negative side effects of using the classic monit / > mongrel_cluster stack with a URL poll by monit is that Rails > generates a > session for every connection. This session is pretty much useless, and > in my case is detrimental to data mining of session activity. > > At this point I am likely to look into the new mod_rails, but I am > wondering if there's any possible way to have external monitors (be it > monit, load balancers, etc) ping a Rails page to verify service, and > yet > _not_ create a session? Due to number of apps & Rails instances, I end > up with 10's of thousands of dummy sessions per day. > > I can provide config setup details, if that's necessary to determine > options, but essentially I have monit call upon a > /public/monit_check.txt file that has no content. this is apparently > enough to still trigger a session via application.rb ? > > Rails 1.2.6, OS X Server 10.5. > > Thanks. > > -- gw --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
