Separate column for network interface stats?
list John Horne
Hello, Using Xymon 4.3.7 I can see network interface graphs for clients in the 'trends' column. However, is it possible to have these graphs displayed in their own 'ifstat' column? Thanks, John. -- John Horne Tel: +XX (X)XXXX XXXXXX Plymouth University, UK Fax: +XX (X)XXXX XXXXXX
list Jeremy Laidman
John
You need three things to make this happen: a) the ifstat page needs to
exist, b) svcstatus.cgi needs to know that graphs exist, and c) an [ifstat]
graph definition must exist in graphs.cfg.
a) The ifstat status page needs to exist, so you could perhaps do this by
adding to clientlaunch.cfg on the client:
[ifstat]
# create a dummy page for ifstat graphs
ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg
CMD /bin/sh -c '$XYMONCLIENTHOME/bin/xymon $XYMSRV \"status
$MACHINE.ifstat green `date`\"'
LOGFILE $XYMONCLIENTLOGS/xymonclient.log
INTERVAL 5m
b) Add ",ifstat" to the TEST2RRD definition.
c) The graphs.cfg provided in the standard code should already have an
[ifstat] section, so nothing to do here.
I'm slightly concerned that TEST2RRD will also be telling xymond_rrd to
create RRD files from the status messages, and that this might interfere
with the standard mechanism for populating these RRD files from the client
data. But I'm guessing that xymond_rrd will simply log a parsing failure
with the status report, and bail, rather than cause any actual problem.
Cheers
Jeremy
▸
On Fri, Jul 20, 2012 at 1:00 AM, John Horne <user-e95f1ec2f147@xymon.invalid>wrote:
Hello, Using Xymon 4.3.7 I can see network interface graphs for clients in the 'trends' column. However, is it possible to have these graphs displayed in their own 'ifstat' column? Thanks, John. -- John Horne Tel: +XX (X)XXXX XXXXXX Plymouth University, UK Fax: +XX (X)XXXX XXXXXX
list John Horne
▸
On Fri, 2012-07-20 at 10:30 +1000, Jeremy Laidman wrote:
John You need three things to make this happen: a) the ifstat page needs to exist, b) svcstatus.cgi needs to know that graphs exist, and c) an [ifstat] graph definition must exist in graphs.cfg.
Hello, Thanks for this. However, I should have thought it through a bit more. What I actually want is to monitor the network interface(s) so that if the bandwidth gets to, say, 70% utilised then we get a yellow status, at 90% we get red. Similar to the 'cpu' and 'disk' monitoring and the LOAD/DISK entries in the analysis.cfg file. I was hoping that something similar was available for the network interfaces (and that we could have a separate column for 'ifstat' as well). I suspect I'll need to write a short script to detect the bandwidth being used by the clients and send the relevant status back to the server.
▸
John.
--
John Horne Tel: +XX (X)XXXX XXXXXX
Plymouth University, UK Fax: +XX (X)XXXX XXXXXX
list Jeremy Laidman
What about adding these line into analysis.cfg to each server you want to
monitor:
DS ifstat ifstat.eth0.rrd:bytesSent >50000000 COLOR=yellow
"TEXT=eth0 &V bytes out is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesReceived >50000000 COLOR=yellow
"TEXT=eth0 &V bytes in is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesSent >70000000 COLOR=red "TEXT=eth0
&V bytes out is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesReceived >70000000 COLOR=red
"TEXT=eth0 &V bytes in is higher than threshold &U"
J
▸
On Mon, Jul 23, 2012 at 10:57 PM, John Horne <user-e95f1ec2f147@xymon.invalid>wrote:
On Fri, 2012-07-20 at 10:30 +1000, Jeremy Laidman wrote:John You need three things to make this happen: a) the ifstat page needs to exist, b) svcstatus.cgi needs to know that graphs exist, and c) an [ifstat] graph definition must exist in graphs.cfg.Hello, Thanks for this. However, I should have thought it through a bit more. What I actually want is to monitor the network interface(s) so that if the bandwidth gets to, say, 70% utilised then we get a yellow status, at 90% we get red. Similar to the 'cpu' and 'disk' monitoring and the LOAD/DISK entries in the analysis.cfg file. I was hoping that something similar was available for the network interfaces (and that we could have a separate column for 'ifstat' as well). I suspect I'll need to write a short script to detect the bandwidth being used by the clients and send the relevant status back to the server. John. -- John Horne Tel: +XX (X)XXXX XXXXXX Plymouth University, UK Fax: +XX (X)XXXX XXXXXX
list John Horne
▸
On Thu, 2012-07-26 at 13:10 +1000, Jeremy Laidman wrote:
What about adding these line into analysis.cfg to each server you want
to monitor:
DS ifstat ifstat.eth0.rrd:bytesSent >50000000 COLOR=yellow
"TEXT=eth0 &V bytes out is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesReceived >50000000 COLOR=yellow
"TEXT=eth0 &V bytes in is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesSent >70000000 COLOR=red
"TEXT=eth0 &V bytes out is higher than threshold &U"
DS ifstat ifstat.eth0.rrd:bytesReceived >70000000 COLOR=red
"TEXT=eth0 &V bytes in is higher than threshold &U"
Interesting! I didn't know analysis.cfg could do that. I'll give it a try tomorrow at work. Thanks. John. -- John Horne, Plymouth University, UK Tel: +XX (X)XXXX XXXXXX Fax: +XX (X)XXXX XXXXXX