Hi Jason,
This timeout is from a stored procedure called clean_old_events. Here
it is:
DELETE FROM status where
DATE_ADD(StateChange, INTERVAL 4 HOUR) < NOW() and severity < 4;
It lives in $ZENHOME/Products/ZenEvents/db/zenprocs.sql. Edit it and
reload it:
$ mysql -pzenoss -uzenoss events < zenprocs.sql
Assuming your username and password are both zenoss.
The events should be preserved in the history.
-Eric
BTW, nice web page.
Jason Quigley wrote:
Hello!
I have noticed that any event with an info severity (2) expire after a
few hours. How is this controlled? I suspected zenmodeler but I shut
it down and they still expire. Is it a cache thing? Where do I change
this?
A bit of background - I have several remote servers and once a day, I
log a bunch of info events which contain hard disk serial numbers,
motherboard info, etc. I'm probably abusing events, but I am unable to
collect this information via snmp as the ports are not open on the
remote routers so it serves as an adequate (and searchable)
replacement. The history is really handy also as we can track disk
replacements, etc.
Many thanks,
Jason.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
