[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Recommendation on setting regular maintenance exclusion for reporting
- To: hobbit (at) hswn.dk
- Subject: RE: [hobbit] Recommendation on setting regular maintenance exclusion for reporting
- From: Ulric Eriksson <ulric (at) siag.nu>
- Date: Sat, 22 Nov 2008 01:43:18 +0100 (CET)
- References: <A3D12FAD74FC8B46991703F40C182BABAB077631 (at) permls102.wde.woodside.com.au> <997a524e0811210723h781e3421ka656169cdccb3b9a (at) mail.gmail.com> <9048B0AD685A48D29032120E75EDDC16 (at) jasonsdell> <Pine.GSO.4.64.0811220054190.27843 (at) solarbob.siag.nu> <363E4AA20D974FCB99B2DDD42F497F6F (at) jasonsdell>
On Fri, 21 Nov 2008, Jason Hand wrote:
These are a variety of monitored entities including windows machines and web
sites.
How would that work as you describe? Do I just substitute the days,
"yourhobbitserver" with the name or localhost, "yourhobbitclient" with the
hostname of the client to disable, "60" with number of minutes to disable
it, and then the "Scheduled reboot" would be the cause?
Right. Actually, "yourhobbitclient" would be, for example:
web1,example,com.cpu
to disable just the cpu test on the client web1.example.com, or
web1,example,com.*
to disable all tests on the same client.
And this cron job would run on the Hobbit server right?
Not necessarily, but that would be a good place to run it.
Ulric