I have several log file monitors set up that keep switching to not supported. I know this happens when the log being checked doesn't exist. Is there a way to prevent this? We have systems that create and write to the log while running and delete it when complete. We need to prevent these monitors from switching to "not supported"
-
-
did you set it to a "Agent (active)" ?
try logrt instead of log as item type (don't know for sure if that works, never tested it.) Will test it on a server in my enviroment
http://www.zabbix.com/documentation/...ypes/log_items -
Thanks for the reply.
Yes, it's set up as an active check.
I tried using logrt (specifically for logs that rotate) but it didn't help. It switched back to not supported after a few minutes since the log file isn't there. I need to find a solution that doesn't reqiure the file to be in place. I don't know how much work it would take to change the behavior of the application.Comment
-
I tested the following:
I created an item with key:
logrt[c:\test\*]
now create a dummy file in that folder. this was picked up with zabbix.
5 min later i created a new file in that folder. Again this was picked up by zabbix!Comment
-
There's a setting in Zabbix that determines how often items that are in a "not supported" state get checked. In the web interface, see Administration -> General -> Other. If the log file being checked is present and readable then the check gets turned back on and runs normally.
This answers my question and hopefully anyone else with the same issue.Comment
Comment