Re: [itm] Omnibus Maintenance

If you're trying to do any type of ITM maintenance, take a look at our
ZapMaintenance agent.  It suppresses events at the situation level in ITM
so that they are never forwarded to omnibus in the first place in case of
scheduled maintenance.

http://www.raygunsoftware.net/products/zapmaintenance-itm-agent

Here's a blog entry with some more detail on how ZapMaintenance can help
when used in conjunction with omnibus event suppression via MWM and others.

http://www.raygunsoftware.net/blog/using-zapmaintenance-for-itm-maintenance-with-tivoli-netcool-omnibus

Thanks,
-- 
Brandon Tallent
Raygun Software
http://www.raygunsoftware.net


On Mon, Nov 26, 2012 at 6:53 AM, Brodeur, Gilles
<[email protected]>wrote:

>  Hi,
>
>
>
> Thanks, I see that I can play with this separate table and SupprEscl
> column.
>
>
>
> But Imagine this scenario :
>
>
>
> I have in place a situation that checks for down scenario of a component
> every 4 hours :
>
>
>
> 01 :00 up
>
> 05 :00 up
>
> 09 :00 down (as scheduled by an approved change order and actual work)
>
> 13 :00 up
>
> 17 :00 down
>
> 23 :00 up
>
>
>
> If a sysadmin puts the server into maintenance mode from 08 :00 to
> 10 :00.  I imagine that I will be alerted at 10 :00 ??
>
>
>
> How can Omnibus know that ITM6 for instance, is heartbeating on long
> intervals?
>
>
>
> thanks
>

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]