[hobbit] need advice

[Kern, Thomas]

My advice is if the custom monitor works for more than 1 client, put it
on the server to centralize it. When it needs to be changed, change it
once on the server and all the client displays get properly changed. 

Now if you need to add data to the client-data stream, you will have to
modify the real hobbit-client script to include the new data, but do it
so that it can run on all clients even if the data is not available on
some client. Then use the server-side processing of client-data to do
the analysis, reporting, alerting and rrdtool updates.

I have a TSM backup reporting script that I run on some of my clients,
but after 4.3 comes out, I will work on including the TSM status data in
the client-data stream and modify the server to analyze it and report on
it.

/Thomas Kern
/301-903-2211  

> -----Original Message-----
> From: Galen Johnson [mailto:gjohnson at trantor.org] 
> Sent: Monday, April 09, 2007 9:06 PM
> To: hobbit at hswn.dk
> Subject: [hobbit] need advice
> 
> Ok, I'm writing a couple of custom monitors for some tasks at the 
> office.  These can be either client or server scripts and can 
> easily be 
> scripted either way.  What would you recommend for server 
> versus client 
> extensions?  What criteria would you use to decide?  Some guidelines 
> would be helpful for determining which type of script to pursue.
> 
> =G=
> 
> 
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
> 
> 
> 
>