Hi Folks,
I am new to Hobbit and noticed that when you drill down to a device's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=procs and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
Hi !
You needs somthing like this in your hobb-client.cfg
PROC firefox 0 -1 TRACK=firefox
http://hswn.dk/hobbit/help/manpages/man5/hobbit-clients.cfg.5.html
The optional TRACK=id setting causes Hobbit to track the number of processes found in an RRD file, and put this into a graph which is shown on the "procs" status display. The id setting is a simple text string which will be used as the legend for the graph, and also as part of the RRD filename. It is recommended that you use only letters and digits for the ID.
Cheers,
MartinOn Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Folks,
I am new to Hobbit and noticed that when you drill down to a device's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=procs and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
Hi Martin and Greg,
Thanks for the reply/suggestion but I do have the TRACK=<id> in the hobbit-clients.cfg file. Below is a snippet of the file:
HOST=wdcacs9.ca.kp.org,silacs9.ssdc.kp.org,coracs9.crdc.kp.org,ndcacs1.nndc.kp.org,ndcacs2.nndc.kp.org PROC CSAdmin.exe 1 1 red TRACK=csadmin PROC CSAuth.exe 1 1 red TRACK=csauth PROC CSDBSync.exe 1 1 red TRACK=csdbsync PROC CSLog.exe 1 1 red TRACK=cslog PROC CSMon.exe 1 1 red TRACK=csmon PROC CSRAdius.exe 1 1 red TRACK=csradius PROC CSTacacs.exe 1 1 red TRACK=cstacacs
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
The hosts that I am monitoring are Windows 2003 servers. I am running BBwin on those servers in local mode. Below is the BBwin.cfg file from one of the servers (this cfg file is the same on all of them):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="goose.ssdc.kp.org" /> <!-- <setting name="bbdisplay" value="yoursecondbbdisplay:port" />--> <!-- BB Pager Part --> <!--<setting name="usepager" value="false" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="pagerlevels" value="red yellow" /> -->
<!-- proxy connection settings -->
<!--
<setting name="useproxy" value="false" />
<setting name="proxy" value="[user:password@]host[:port]'/>
-->
<!-- bbwin mode local or central -->
<setting name="mode" value="local" />
<setting name="configclass" value="win32" />
<setting name="autoreload" value="true" />
<setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/>
<load name="disk" value="disk.dll"/>
<load name="externals" value="externals.dll"/>
<load name="filesystem" value="filesystem.dll"/>
<load name="memory" value="memory.dll"/>
<load name="msgs" value="msgs.dll"/>
<load name="procs" value="procs.dll"/>
<load name="stats" value="stats.dll"/>
<load name="svcs" value="svcs.dll"/>
<load name="uptime" value="uptime.dll"/>
<load name="who" value="who.dll"/>
<setting name="loglevel" value="3" />
<setting name="logpath" value="C:\Program Files\BBWin\logs\BBWin.log"/> <!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="false" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="85%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="E" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will check that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <!-- externals launch examples <load value="cscript mybbscript.vbs" /> <load value="myexternal.exe" /> <load value="cscript wlbs.vbs" timer="15m" /> <load value="cluster.exe" timer="90s" /> --> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="78" paniclevel="98" /> <setting name="page" warnlevel="70" paniclevel="90" /> <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs> <setting name="alwaysgreen" value="false" /> <setting name="delay" value="30m" /> <match logfile="System" type="error" alarmcolor="red" /> <match logfile="System" type="warning" alarmcolor="yellow" /> <match logfile="Application" type="error" alarmcolor="red" /> <match logfile="Application" type="warning" alarmcolor="yellow" /> <match logfile="Security" type="fail" /> <ignore logfile="Application" source="BigBrotherHobbitClient" type="warning" /> <ignore logfile="System" source="W32Time" type="error" /> <ignore logfile="System" source="W32Time" type="warning" /> <ignore logfile="System" source="Perflib" type="warning" /> <ignore logfile="System" source="TermServDevices" type="warning" /> <ignore logfile="System" source="TermServDevices" type="error" /> <ignore logfile="System" eventid="7001" source="Service Control Manager" type="error" /> <ignore logfile="Security" eventid="529" source="Security" type="Failure" /> <ignore logfile="Security" eventid="535" source="Security" type="Failure" /> <ignore logfile="Security" eventid="537" source="Security" type="Failure" /> <ignore logfile="Security" eventid="539" source="Security" type="Failure" /> <ignore logfile="Security" eventid="577" source="Security" type="Failure" /> <ignore logfile="Security" eventid="680" source="Security" type="Failure" />
<!-- Some ignore rules examples
<ignore logfile="Application" eventid="1030" />
<ignore logfile="System" source="W32Time" />
--></msgs> <procs> <!-- <setting name="CSAdmin.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSLog.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSMon.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="yellow" /> --> <setting name="CSAdmin.exe" rule="=1" alarmcolor="red" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="red" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="red" /> <setting name="CSLog.exe" rule="=1" alarmcolor="red" /> <setting name="CSMon.exe" rule="=1" alarmcolor="red" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="red" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="red" />
<!-- some procs rules example
<setting name="drwtsn" rule="-1" alarmcolor="red" />
<setting name="pageant.exe" rule="=1" comment="Putty agent deamon" /> --> </procs> <svcs> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- If true, the agent will restart all "automatic services" which would be stopped--> <setting name="autoreset" value="false" /> <setting name="alarmcolor" value="red" /> <setting name="delay" value="3m" /> <!-- <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="yellow"/> --> <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="red"/>
<!-- The line bellow show you svcs rules. If the "Automatic Updates" service is stopped, it will be automatically restarted and a red status will be sent until the service get it's correct status <setting name="Automatic Updates" value="started" autoreset="true" alarmcolor="red" /> --> </svcs> <uptime> <setting name="delay" value="30m" /> <setting name="maxdelay" value="3650d" /> </uptime> </configuration>
Thanks!
Ann
Martin Flemming <martin.flemming at desy.de> 09/03/2008 08:45 AM Please respond to hobbit at hswn.dk
To hobbit at hswn.dk cc
Subject Re: [hobbit] No Procs Graph?
Hi !
You needs somthing like this in your hobb-client.cfg
PROC firefox 0 -1 TRACK=firefox
http://hswn.dk/hobbit/help/manpages/man5/hobbit-clients.cfg.5.html
The optional TRACK=id setting causes Hobbit to track the number of processes found in an RRD file, and put this into a graph which is shown on the "procs" status display. The id setting is a simple text string which will be used as the legend for the graph, and also as part of the RRD filename. It is recommended that you use only letters and digits for the ID.
Cheers,
MartinOn Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Folks,
I am new to Hobbit and noticed that when you drill down to a device's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to
http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=procs
and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi !
Puh, unfortunately i've got no BBwin-experience ..
sorry ...
have you ask/check on
https://lists.sourceforge.net/lists/listinfo/bbwin-users or http://sourceforge.net/forum/forum.php?forum_id=460874
cheers, martin
On Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Martin and Greg,
Thanks for the reply/suggestion but I do have the TRACK=<id> in the hobbit-clients.cfg file. Below is a snippet of the file:
HOST=wdcacs9.ca.kp.org,silacs9.ssdc.kp.org,coracs9.crdc.kp.org,ndcacs1.nndc.kp.org,ndcacs2.nndc.kp.org PROC CSAdmin.exe 1 1 red TRACK=csadmin PROC CSAuth.exe 1 1 red TRACK=csauth PROC CSDBSync.exe 1 1 red TRACK=csdbsync PROC CSLog.exe 1 1 red TRACK=cslog PROC CSMon.exe 1 1 red TRACK=csmon PROC CSRAdius.exe 1 1 red TRACK=csradius PROC CSTacacs.exe 1 1 red TRACK=cstacacs
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
The hosts that I am monitoring are Windows 2003 servers. I am running BBwin on those servers in local mode. Below is the BBwin.cfg file from one of the servers (this cfg file is the same on all of them):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="goose.ssdc.kp.org" /> <!-- <setting name="bbdisplay" value="yoursecondbbdisplay:port" />--> <!-- BB Pager Part --> <!--<setting name="usepager" value="false" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="pagerlevels" value="red yellow" /> -->
<!-- proxy connection settings --> <!-- <setting name="useproxy" value="false" /> <setting name="proxy" value="[user:password@]host[:port]'/> --> <!-- bbwin mode local or central --> <setting name="mode" value="local" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="5m" /> <load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/> <setting name="loglevel" value="3" /> <setting name="logpath" value="C:\ProgramFiles\BBWin\logs\BBWin.log"/> <!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="false" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="85%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="E" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will check that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <!-- externals launch examples <load value="cscript mybbscript.vbs" /> <load value="myexternal.exe" /> <load value="cscript wlbs.vbs" timer="15m" /> <load value="cluster.exe" timer="90s" /> --> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="78" paniclevel="98" /> <setting name="page" warnlevel="70" paniclevel="90" /> <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs> <setting name="alwaysgreen" value="false" /> <setting name="delay" value="30m" /> <match logfile="System" type="error" alarmcolor="red" /> <match logfile="System" type="warning" alarmcolor="yellow" /> <match logfile="Application" type="error" alarmcolor="red" /> <match logfile="Application" type="warning" alarmcolor="yellow" /> <match logfile="Security" type="fail" /> <ignore logfile="Application" source="BigBrotherHobbitClient" type="warning" /> <ignore logfile="System" source="W32Time" type="error" /> <ignore logfile="System" source="W32Time" type="warning" /> <ignore logfile="System" source="Perflib" type="warning" /> <ignore logfile="System" source="TermServDevices" type="warning" /> <ignore logfile="System" source="TermServDevices" type="error" /> <ignore logfile="System" eventid="7001" source="Service Control Manager" type="error" /> <ignore logfile="Security" eventid="529" source="Security" type="Failure" /> <ignore logfile="Security" eventid="535" source="Security" type="Failure" /> <ignore logfile="Security" eventid="537" source="Security" type="Failure" /> <ignore logfile="Security" eventid="539" source="Security" type="Failure" /> <ignore logfile="Security" eventid="577" source="Security" type="Failure" /> <ignore logfile="Security" eventid="680" source="Security" type="Failure" />
<!-- Some ignore rules examples <ignore logfile="Application" eventid="1030" /> <ignore logfile="System" source="W32Time" /> --></msgs> <procs> <!-- <setting name="CSAdmin.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSLog.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSMon.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="yellow" /> --> <setting name="CSAdmin.exe" rule="=1" alarmcolor="red" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="red" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="red" /> <setting name="CSLog.exe" rule="=1" alarmcolor="red" /> <setting name="CSMon.exe" rule="=1" alarmcolor="red" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="red" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="red" />
<!-- some procs rules example <setting name="drwtsn" rule="-1" alarmcolor="red" /> <setting name="pageant.exe" rule="=1" comment="Putty agent deamon"/> --> </procs> <svcs> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- If true, the agent will restart all "automatic services" which would be stopped--> <setting name="autoreset" value="false" /> <setting name="alarmcolor" value="red" /> <setting name="delay" value="3m" /> <!-- <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="yellow"/> --> <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="red"/>
<!-- The line bellow show you svcs rules. If the "AutomaticUpdates" service is stopped, it will be automatically restarted and a red status will be sent until the service get it's correct status <setting name="Automatic Updates" value="started" autoreset="true" alarmcolor="red" /> --> </svcs> <uptime> <setting name="delay" value="30m" /> <setting name="maxdelay" value="3650d" /> </uptime> </configuration>
Thanks!
Ann
Martin Flemming <martin.flemming at desy.de> 09/03/2008 08:45 AM Please respond to hobbit at hswn.dk
To hobbit at hswn.dk cc
Subject Re: [hobbit] No Procs Graph?
Hi !
You needs somthing like this in your hobb-client.cfg
PROC firefox 0 -1 TRACK=firefox
http://hswn.dk/hobbit/help/manpages/man5/hobbit-clients.cfg.5.html
The optional TRACK=id setting causes Hobbit to track the number of processes found in an RRD file, and put this into a graph which is shown on the "procs" status display. The id setting is a simple text string which will be used as the legend for the graph, and also as part of the RRD filename. It is recommended that you use only letters and digits for the ID.
Cheers,
MartinOn Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Folks,
I am new to Hobbit and noticed that when you drill down to a device's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to
http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=procs
and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Thanks, Martin, I'll do that!
Regards,
Ann
Martin Flemming <martin.flemming at desy.de> 09/03/2008 12:24 PM Please respond to hobbit at hswn.dk
To hobbit at hswn.dk cc
Subject Re: [hobbit] No Procs Graph?
Hi !
Puh, unfortunately i've got no BBwin-experience ..
sorry ...
have you ask/check on
https://lists.sourceforge.net/lists/listinfo/bbwin-users or http://sourceforge.net/forum/forum.php?forum_id=460874
cheers, martin
On Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Martin and Greg,
Thanks for the reply/suggestion but I do have the TRACK=<id> in the hobbit-clients.cfg file. Below is a snippet of the file:
HOST=wdcacs9.ca.kp.org,silacs9.ssdc.kp.org,coracs9.crdc.kp.org,ndcacs1.nndc.kp.org,ndcacs2.nndc.kp.org
PROC CSAdmin.exe 1 1 red TRACK=csadmin PROC CSAuth.exe 1 1 red TRACK=csauth PROC CSDBSync.exe 1 1 red TRACK=csdbsync PROC CSLog.exe 1 1 red TRACK=cslog PROC CSMon.exe 1 1 red TRACK=csmon PROC CSRAdius.exe 1 1 red TRACK=csradius PROC CSTacacs.exe 1 1 red TRACK=cstacacsDEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
The hosts that I am monitoring are Windows 2003 servers. I am running BBwin on those servers in local mode. Below is the BBwin.cfg file from one of the servers (this cfg file is the same on all of them):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="goose.ssdc.kp.org" /> <!-- <setting name="bbdisplay" value="yoursecondbbdisplay:port" />--> <!-- BB Pager Part --> <!--<setting name="usepager" value="false" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="pagerlevels" value="red yellow" /> -->
<!-- proxy connection settings --> <!-- <setting name="useproxy" value="false" /> <setting name="proxy" value="[user:password@]host[:port]'/> --> <!-- bbwin mode local or central --> <setting name="mode" value="local" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="5m" /> <load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/> <setting name="loglevel" value="3" /> <setting name="logpath" value="C:\ProgramFiles\BBWin\logs\BBWin.log"/> <!-- If true, the agent will report reporting failures as
warning
events --> <setting name="logreportfailure" value="false" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="85%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="E" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will check that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <!-- externals launch examples <load value="cscript mybbscript.vbs" /> <load value="myexternal.exe" /> <load value="cscript wlbs.vbs" timer="15m" /> <load value="cluster.exe" timer="90s" /> --> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="78" paniclevel="98" /> <setting name="page" warnlevel="70" paniclevel="90" /> <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs> <setting name="alwaysgreen" value="false" /> <setting name="delay" value="30m" /> <match logfile="System" type="error" alarmcolor="red" /> <match logfile="System" type="warning" alarmcolor="yellow" /> <match logfile="Application" type="error" alarmcolor="red" /> <match logfile="Application" type="warning" alarmcolor="yellow" /> <match logfile="Security" type="fail" /> <ignore logfile="Application" source="BigBrotherHobbitClient" type="warning" /> <ignore logfile="System" source="W32Time" type="error" /> <ignore logfile="System" source="W32Time" type="warning" /> <ignore logfile="System" source="Perflib" type="warning" /> <ignore logfile="System" source="TermServDevices" type="warning" /> <ignore logfile="System" source="TermServDevices" type="error" /> <ignore logfile="System" eventid="7001" source="Service Control Manager" type="error" /> <ignore logfile="Security" eventid="529" source="Security" type="Failure" /> <ignore logfile="Security" eventid="535" source="Security" type="Failure" /> <ignore logfile="Security" eventid="537" source="Security" type="Failure" /> <ignore logfile="Security" eventid="539" source="Security" type="Failure" /> <ignore logfile="Security" eventid="577" source="Security" type="Failure" /> <ignore logfile="Security" eventid="680" source="Security" type="Failure" />
<!-- Some ignore rules examples <ignore logfile="Application" eventid="1030" /> <ignore logfile="System" source="W32Time" /> --></msgs> <procs> <!-- <setting name="CSAdmin.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSLog.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSMon.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="yellow" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="yellow" /> --> <setting name="CSAdmin.exe" rule="=1" alarmcolor="red" /> <setting name="CSAuth.exe" rule="=1" alarmcolor="red" /> <setting name="CSDBSync.exe" rule="=1" alarmcolor="red" /> <setting name="CSLog.exe" rule="=1" alarmcolor="red" /> <setting name="CSMon.exe" rule="=1" alarmcolor="red" /> <setting name="CSRAdius.exe" rule="=1" alarmcolor="red" /> <setting name="CSTacacs.exe" rule="=1" alarmcolor="red" />
<!-- some procs rules example <setting name="drwtsn" rule="-1" alarmcolor="red" /> <setting name="pageant.exe" rule="=1" comment="Putty agentdeamon" /> --> </procs> <svcs> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- If true, the agent will restart all "automatic services" which would be stopped--> <setting name="autoreset" value="false" /> <setting name="alarmcolor" value="red" /> <setting name="delay" value="3m" /> <!-- <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="yellow"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="yellow"/> --> <setting name="CSAdmin" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSAuth" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSDbSync" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSLog" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSMon" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSRadius" value="started" autoreset="false" alarmcolor="red"/> <setting name="CSTacacs" value="started" autoreset="false" alarmcolor="red"/>
<!-- The line bellow show you svcs rules. If the "AutomaticUpdates" service is stopped, it will be automatically restarted and a red status will be sent until the service get it's correct status <setting name="Automatic Updates" value="started" autoreset="true" alarmcolor="red" /> --> </svcs> <uptime> <setting name="delay" value="30m" /> <setting name="maxdelay" value="3650d" /> </uptime> </configuration>
Thanks!
Ann
Martin Flemming <martin.flemming at desy.de> 09/03/2008 08:45 AM Please respond to hobbit at hswn.dk
To hobbit at hswn.dk cc
Subject Re: [hobbit] No Procs Graph?
Hi !
You needs somthing like this in your hobb-client.cfg
PROC firefox 0 -1 TRACK=firefox
http://hswn.dk/hobbit/help/manpages/man5/hobbit-clients.cfg.5.html
The optional TRACK=id setting causes Hobbit to track the number of processes found in an RRD file, and put this into a graph which is shown on the "procs" status display. The id setting is a simple text string which will be used as the legend for the graph, and also as part of the RRD filename. It is recommended that you use only letters and digits for the ID.
Cheers,
MartinOn Wed, 3 Sep 2008, Ann.Waters at kp.org wrote:
Hi Folks,
I am new to Hobbit and noticed that when you drill down to a device's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to
http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=procs
and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Ann,
The procs page will graph anything you want to count. You enable this with the TRACK keyword in (I think) the hobbit-clients.cfg file.
For example:
HOST=somehost PROC httpd TRACK=Apache
Would lead to a graph showing the number of processes containing "httpd" in their name, graphed as "Apache".
If you want graphs about particular processes (memory usage, CPU, etc.) you are out of luck in this version of Hobbit, although you could probably invent something that would read through the process listings returned by the Hobbit clients and have them update RRD's and then set up graph definitions. This would be a lot of work, and might overload the poor Hobbit server depending on how many clients you are monitoring.
GLH
From: Ann.Waters at kp.org [mailto:Ann.Waters at kp.org]
Sent: Wednesday, September 03, 2008 7:08 AM
To: hobbit at hswn.dk
Subject: [hobbit] No Procs Graph?
Hi Folks,
I am new to Hobbit and noticed that when you drill down to adevice's procs information, there is no graph but the magnifying glass shows up as if a graph should be there. I've looked through so many man pages, wiki entries, FAQs, etc. trying to figure this out that my head is spinning! And when I go to the Hobbit demo site and drill down to http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=voodoo.hswn.dk&SERVICE=proc s and http://hswn.dk/hobbit-cgi/bb-hostsvc.sh?HOST=sarge&SERVICE=procs, the procs graphs don't show up there either. So, have I been wasting my time trying to make that graph work or is there some magical trick that a master is willing to reveal to me?
Any/all help will be appreciated!
Thanks!
Ann
participants (3)
-
Ann.Waters＠kp.org
-
greg.hubbard＠eds.com
-
martin.flemming＠desy.de