Log file monitoring on Windows Server

[Maveric]

I cannot managed to monitor a log file on a Windows server 2003 by using a Zabbix agent (active) item with the type 'log' and log[path_to_the_file] as key.

I'm not sure to use the proper key as log[] doesn't show in the Windows Zabbix Agent list of supported parameters.
I'm also not sure if this feature is actually supported !

Any help would be greatly appreciated.

Thanks

___________
Zabbix 1.3.1 on Fedora core 6

[niak]

I've got the same problem,

Is it supported by windows agent ?

[niak]

hi,

This is my key:

log[c:\zabbix_agentd.log,aucune]

And error :
Not supported by agent !



Zabbix can not monitored log file of windows ?

[Alexei]

Monitoring of log files is supported by ZABBIX! Something is incorrectly configured

[trikke]

Hi,

this happens to me if I configure a nonexisting file??? This is a standard Zabbix error message if something is wrong with the "Monitor".

To narrow your problem, go to the windows box and search the Zabbix_agentd.log File for errors ( maybe set debug level to 5).

Logfile Messages of interest are:
get_active_checks
parse_list_of_checks
In process log

now u schould have a clue of what is going on!!!


Don't forget DisableActive=0 and the Hostname= parameter as described in:

http://www.zabbix.com/forum/showthread.php?t=7935

Greetings

[niak]

Thank you for reply,

-Hostname matches name host of the host configured in ZABBIX frontend!
-DisableActive=0
-In zabbix_agentd.log:
2160:20080117:161651 get_active_checks('192.168.1.75',10051)
2160:20080117:161651 Sending [ZBX_GET_ACTIVE_CHECKS
Pc_Guillaume
]
2160:20080117:161651 Before read
2160:20080117:161651 In parse_list_of_checks() [log[c:\zabbix_agentd.log,aucune]:1:336462
ZBX_EOF
]
2160:20080117:161651 In disable_all_metrics()
2160:20080117:161651 Parsed [log[c:\zabbix_agentd.log,aucune]:1:336462]
2160:20080117:161651 In add_check('log[c:\zabbix_agentd.log,aucune]', 1, 336462)
2160:20080117:161651 Parsed [ZBX_EOF]
2160:20080117:161651 In process_active_checks('192.168.1.75',10051)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177619)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177688)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177757)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177826)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177895)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,177964)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178033)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178102)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178171)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178240)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178287)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178334)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178378)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178422)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178469)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178510)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178554)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178598)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178663)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178710)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178781)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178850)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178919)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,178988)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179057)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179126)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179195)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179264)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179333)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179402)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179471)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179540)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179609)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179678)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179747)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179816)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179885)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,179954)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,180023)
2160:20080117:161651 In process log (c:\zabbix_agentd.log,180092)
2160:20080117:161651 In get_min_nextcheck()
2160:20080117:161651 Sleeping for 1 seconds

[trikke]

Hmm,

looks like your agent is parsing the log-file, but i don't see a match ( Sending something to the Server ;-)), r'u shure this string "aucune" will be found??? Try
"process"

On the server side, see if u configured the item corectly ( type log or text, try out!!!)

Greets
Patrick

[niak]

THANK YOU trikke,

The problem was the type of information in the item: it was set to "Log" as the documentation recomended it !
I set Type of information on: "Text" and the problem is solved !

However, in the list of item , the item status stay on " Not supported by agent"!

Thank you very much

[Monitoring]

Complete solution

It is a long time ago for you,

But I have made a solution / tutorial for this.
In your case.. set the agent active... in the agent config file... and you are ready.

from 2009, are you still working with zabbix?? I am a newbie.. so perphaps you will / can help me with some stuff.

Thanks for your reply.
Greets Gerard

Sorry, I've forget the link:

http://www.zabbix.com/forum/showthre...6823#post76823