Hi,
I use the PrimeAlert LogFileAlert module from Halcyon to monitor a logfile on a windows server (scan mode incremental).
If I set an Alarm Window to "Time >= 10:00:00" to get only alarms after 10:00, the console window at 10:00 hours shows me an alarm created much earlier than 10:00 !?
Works this as designed?
Best regards
Oliver
Hi Oliver,
This is probably a question for Halcyon support, since it has some features that are different from Sun's "File Scanning" log module...
> I use the PrimeAlert LogFileAlert module from Halcyon
> to monitor a logfile on a windows server (scan mode
> incremental).
> If I set an Alarm Window to "Time >= 10:00:00" to get
> only alarms after 10:00, the console window at 10:00
> hours shows me an alarm created much earlier than
> 10:00 !?
This is actually how it's designed: in fact that feature is baked into all alarm windows in SunMC. The window doesn't control when alarms are detected... just when you are told about them.
You could try the Module Enable/Disable time window instead to see if that does what you want (i.e. the module is entirely turned off until the time you specify). Or, if you're module supports it, try using the Reset tab so your pattern counter resets to zero just before your Alarm Window goes active (i.e. reset the counter to zero at 08:59:30 before the Alarm Window activates at 09:00:00)
An example of the Reset options can be found here: (search for "Resetting the Matches Column" near the bottom of the page)
http://www.halcyoninc.com/products/PlusPack/help/LogFileMonitor/HALLogFileAlert -patterns-h.html
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
Hi Mike,
Thank you for your help!
Module Enable/Disable doesn磘 work as expected: a line inserted before the time window will be reported as new alarm.
Reset Counter Schedule would be nice but is not available in FileScanning Module for Windows.
I don磘 need alarms created outside my Alarm Window. Do I have no other chance to prevent such "old" Alarms?
Regards,
Oliver
