|
||||||||||
I think that that would be taking m0n0 away from it's target of embedded use, however the idea does bring up some thoughts as to data available via SNMP. I too use cacti, and am very happy with it, but it would be nice if things like CPU and memory useage were available so they could be monitored from a different system running Cacti or other SNMP program. Dan On Sat, 05 Mar 2005 10:43:45 +0100, Christian Rohmann <Christian dot Rohmann at gmx dot de> wrote: > Nothing against svg graphs ... they made me smile when 1st seeing > m0n0wall on screenshots. > > But as we already have snmp and php installed now about a real > monitoring over time: > > http://www.cacti.net/ > > Admitted that for that we would need a small partition to save the data > on. In memory you always lose the data in a reboot. > > With cacti we could just monitor whatever we feel like in any > summarization. Actually everything that snmp and local scripts can do -> > everything :-) > > Hope this is not some suggestion that is against the way m0n0wall is > planned, but real time graphs don't show problems with CPU / memory / > bandwidth over time and there might be a job running over VPN during the > night and you don't see the peak it has on the CPU and so on ... > > Take care > > Christian > > > Norman H. Azadian wrote: > > > While we're wishing, I'd like to see a graph of queue lengths. > > > > NHA > > --- > > Norman H. Azadian Taegerishalde 13 CH-3110 Muensingen > > Switzerland > > norman at azadian dot ch tel: +41 31 721 7855 fax: +41 31 55 898 55 > > > > > > Braden McGrath wrote: > > > >> It shouldn't be too hard, although having it be clickable ON the graphs > >> may not be too easy. clicking a button to choose which line to "focus" > >> should be easy though... I was thinking the same thing, some sort of > >> "graphs" section that holds one or more SVG graphs would be cool. IMHO, > >> it'd be better to do traffic on one and mem/cpu on another... and then > >> give options for which interfaces you'd like to show. it'd be even > >> cooler if you could somehow get a graph of ALL total traffic going > >> through the m0n0, although I don't know how easy it would be to graph > >> all traffic without getting a lot of duplicate data (for things that > >> went in opt1 and out on LAN, for instance). > >> > >> --Braden > >> > >>> -----Original Message----- > >>> From: Joey Morin [mailto:joeymorin at gmail dot com] Sent: Friday, March > >>> 04, 2005 1:19 PM > >>> To: m0n0wall at lists dot m0n0 dot ch > >>> Subject: Re: [m0n0wall] Re: Beta 1.2b6 > >>> > >>> On Wed, 02 Mar 2005 10:55:23 -0500, Jesse Guardiani > >>> <jesse at wingnet dot net> wrote: > >>> > >>>> Manuel Kasper wrote: > >>>> > >>>> > >>>>> Furthermore, the CPU meter on the index page is gone - it > >>>> > >>> > >>> has been > >>> > >>>>> replaced by an SVG graph. > >>>> > >>>> > >>>> Thanks for the new release! The bug fixes are much > >>> > >>> > >>> appreciated, and I > >>> > >>>> particularly like the new SVG CPU graph! Very cool! > >>> > >>> > >>> love the CPU graph. it's helpful to see the traffic graph and cpu > >>> graph at the same time. i can see what kind of a hit the m0n0 is > >>> taking with different kinds of traffic. especially useful for VPN. > >>> > >>> however, i have to have two browser windows open to see both cpu and > >>> traffic at the same time. and, they don't seem to be updating at > >>> the same rate. looks like the cpu graph updates at 1 second > >>> intervals, while the traffic graph updates at 2 second intervals. > >>> it's hard to compare the two. > >>> > >>> perhpas all three (or more) traces (cpu, WAN and LAN, and other > >>> interfaces) could be combined into one single SVG graph? perhaps > >>> clickable to select which traces to display (like the bytes/bits and > >>> up/follow)? > >>> > >>> i suggest this, of course, having no idea how hard that would be to > >>> do :) > >>> > >>> love the m0n0. > >>> > >>> jj > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > >>> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > >>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > >> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > |