Log monitoring, UCS2-LE encoding bug on zabbix 3.2 version.

[ozzabix]

Zabbix 3.0.8 version log monitoring UCS2-LE working normaly.
I tested on CENTOS 7.2,ZABBIX 3.2.x log monitoring on windows server 2012 MSSQLSERVER Errorlog.
My zabbix key active "log["D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG",failed ,utf-16le] and it is not working.


SQL server Error log encoding UCS2-LE BOM.

We tried all alternative way file encoding,UCS2-LE or UTF-16 on windows server etc. But not changed issue.

[ozzabix]

vfs.file.regexp["D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG&qu ot;,Lo gin failed,UTF-16]

Zabbix 3.0.8 version log monitoring UCS2-LE working normaly.
I tested on CENTOS 7.2,ZABBIX 3.2.x log monitoring on windows server 2012 MSSQLSERVER Errorlog.
My zabbix key active "log["D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG",failed ,utf-16le] and it is not working.


SQL server Error log encoding UCS2-LE BOM.

We tried all alternative way file encoding,UCS2-LE or UTF-16 on windows server etc. But not changed issue.

Hello,
vfs.file.regexp["D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG",Lo gin failed,UTF-16] worked encoding.

[ozzabix]

Result is OK

Hello last result is worked perfectly on zabbiz-server 3.2.1

log["D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG","L ogin failed for user",UTF-16]