question on how filters work.
Posted: Tue Jun 06, 2006 11:31 pm
So I used the purgewhenfull filter (as suggested in the faq/readme :) to delete events when the disk gets over 90% full.
I'm confused about the difference between a filter that is saved and when it is executed.
Does the filter stay and get executed indefinately, or is it a one time shot?
If it's a one time thing, do most people just run a cron job to trigger the filter?
Does the filter apply only to one monitor or can it apply to all of them?
And the readme warns about limiting what is returned from the filter, otherwise all events would be deleted. Am I reading that right? How do I avoid this problem?
Thanks!
E
I'm confused about the difference between a filter that is saved and when it is executed.
Does the filter stay and get executed indefinately, or is it a one time shot?
If it's a one time thing, do most people just run a cron job to trigger the filter?
Does the filter apply only to one monitor or can it apply to all of them?
And the readme warns about limiting what is returned from the filter, otherwise all events would be deleted. Am I reading that right? How do I avoid this problem?
Thanks!
E