okay, that makes sense. i was thinking this method was separate from zenoss, but i re-read and see it's not. yeah, i have the delay set in my alerting rules already. the ultimate problem is this weird inconsistency, that one process gets reported down but then automatically cleared, while the other never clears. it's a hair-puller. who knows, maybe it's something wrong with my regex. the mongrel_rails process line is actually quite long, while the memcached process is very short -
memcached: /usr/bin/memcached -p 11211 -u nobody -m 128 mongrel: /usr/bin/ruby /usr/bin/mongrel_rails start -d -e production -c /u/apps/core/current --user rails --group rails -p 8000 -P /u/apps/core/shared/pids/mongrel.8000.pid -l log/mongrel.8000.log and there's one instance each for ports 8000 to 8014, so each instance is slightly different. however, i had thought that setting 'ignore parameters' true, and disabling 'zCountProcs' would handle that - but apparently not. heck, the fact that the processes have all been up since july 3 - even though i got paged that they were down on july 6 - that's really the crux of the matter. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22243#22243 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
