Xymon Mailing List Archive search

multiple apache instance trending question

list Tom L. Stewart
Wed, 30 Jan 2008 13:54:13 -0600
Message-Id: <user-4d7cf213fc75@xymon.invalid>

We did a simpler method of just creating additional hosts for the
different apaches (by port number) like so (in bb-hosts).

 
0.0.0.0         hostname-80     # noconn http://xxx.xxx.xxx.xxx:80/
apache TRENDS:

*,apache:apache|apache1|apache2|apache3

0.0.0.0         hostname-8080     # noconn http://xxx.xxx.xxx.xxx:8080/
apache TRENDS:

*,apache:apache|apache1|apache2|apache3

 
Where xxx = ip address

 
Tom

 
From: user-d0c05d6d01c9@xymon.invalid [mailto:user-d0c05d6d01c9@xymon.invalid] 
Sent: Tuesday, January 29, 2008 2:27 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] multiple apache instance trending question

 
I have a new hobbit installation which is collecting and trending the
apache status data correctly. 

For various reasons, I have about 7 separate apache instances on each
server that I would like to trend individually as well. 

To accomplish this, I think that I would have to do the following in
order to get hobbit (4.2.0)  to trend this data: 

edit ~/bbnet/bbtest-net.c and copy the apache section (lines 601-637)
the requisite number of times changing the subsequent apache references
to something like 2apache, then 3apache, etc. 
Modify the  ~/hobbitd/rrd/do_apache.c file basically copying the entire
thing starting at line 13 (int do_apache_rrd(char *hostname, char
*testname, char *msg, time_t tstamp) but changing each instance of
apache to 2apache, then 3apache, etc. Then recompile and redeploy. 

After redeploying, I would also need to modify hobbitgraph.cfg copying
the apache section and modifying with 2apache, 3apache, etc for the name
of the graph as well as the rrd files. 

At this point, I think I should point out that I don't program in C
(many would say in any other language either.) 

Is there anything else that I am missing? and am I making this too hard?


steve 


steve mcconnell
gsk
unix application hosting support
XXX-XXX-XXXX