Hey all, I''m not sure where the Gauge discussion tends to happen, or who is driving Gauge development. I have some concerns that the way it''s being developed will lead to either (1) a weak implementation, without the essential network monitoring features present in e.g., Munin and Nagios, or (2) a slow implementation when monitoring large networks, or [worse] (3) a situation where Rails stats aren''t available to the more robust toolsets. I''m sure these concerns can be resolved with just a bit of discussion. Both Odeo and myself would be happy to contribute to Gauge development, but it must work with our existing network monitoring tools. Rails is the central component, but still just a component in a larger system, and that larger system must be accounted for. thanks! b.
Blaine, We''d love to have your input, naturally. However, please keep in mind a few things: 1. We do not currently intend for gauge to be a replacement for (or even necessarily integrate with) systems like nagios. 2. Gauge is slated only to report real-time stats for Rails applications, along with (possibly) a few system-related variables (like load). 3. Gauge will be a small tool, to scratch a small (but important) itch, which is primarily the gathering of performance statistics in real-time. With those bullet-points in mind, we would appreciate any input and suggestions. Also, the above points are only for the first release. It may be that, down the road, we will decide to integrate with (or even *gasp* replace) something like nagios, but it would only hurt the project at this point to work with that goal as primary. - Jamis On Oct 19, 2005, at 3:13 PM, Blaine Cook wrote:> Hey all, > > I''m not sure where the Gauge discussion tends to happen, or who is > driving Gauge development. I have some concerns that the way it''s > being developed will lead to either (1) a weak implementation, > without the essential network monitoring features present in e.g., > Munin and Nagios, or (2) a slow implementation when monitoring > large networks, or [worse] (3) a situation where Rails stats aren''t > available to the more robust toolsets. > > I''m sure these concerns can be resolved with just a bit of > discussion. Both Odeo and myself would be happy to contribute to > Gauge development, but it must work with our existing network > monitoring tools. Rails is the central component, but still just a > component in a larger system, and that larger system must be > accounted for. > > thanks! > > b. > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core >
> I''m not sure where the Gauge discussion tends to happen, or who is > driving Gauge development. I have some concerns that the way it''s > being developed will lead to either (1) a weak implementation, > without the essential network monitoring features present in e.g., > Munin and Nagios, or (2) a slow implementation when monitoring large > networks, or [worse] (3) a situation where Rails stats aren''t > available to the more robust toolsets.Thanks for your concerns, Blaine. But for now we''re just taking one step at the time. Getting Real and all that jazz. Round one is mostly about getting statistical data processed from the requests. Not about monitoring networks or server health. That might happen down the road, but it''s not the next step. So we are very much aiming to have a "weak implementation, without the essential network monitoring features" for the first release. I wouldn''t uninstall all your other server management gear just yet. But do have a look and give us feedback when the first packaged release of Gauge comes around.> I''m sure these concerns can be resolved with just a bit of > discussion. Both Odeo and myself would be happy to contribute to > Gauge development, but it must work with our existing network > monitoring tools. Rails is the central component, but still just a > component in a larger system, and that larger system must be > accounted for.We''ll be happy to entertain discussion as soon as we have something real. We''d definitely love to get feedback from other high-load users when the system is ready. -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework