<![CDATA[LOGWATCH: issues when parsing files with ISO-8859-1 encoding]]>Hi,

Isn't it possible to parse files with ISO-8859-1 encoding using LOGWATCH?

I created a test using the following configuration:

<parser trace="7">
    <file>d:\demo.txt</file>
    <rules>
        <rule>
            <match>[0-9]{3}</match>
            <event>100000</event>
        </rule>
    </rules>
</parser>

When I save a file with 123 as the content the parser will match if it is saved with UTF-8 encoding and it won't match if it is saved with ISO-8859-1 encoding.

Did I forget a setting or is still as intended?

The log that I need to monitor will be in ISO-8859.

I installed the nxagent-1.2.6-x64 agent and it is running on a Windows 2003 R2 x64 server.

Regards,

Jos

]]>https://forum.netxms.org/topic/2241/logwatch-issues-when-parsing-files-with-iso-8859-1-encodingRSS for NodeFri, 13 Nov 2026 20:48:48 GMTFri, 08 Mar 2013 16:47:06 GMT60<![CDATA[Reply to LOGWATCH: issues when parsing files with ISO-8859-1 encoding on Sat, 09 Mar 2013 19:21:38 GMT]]>Hi Victor,

These are the two files I used while testing.
The 123 in the ANSI file isn't seen as a match, the 123 in the UTF-8 file matches.

Cheers,

Jos

demo_ANSI.txt

demo_UTF-8.txt

]]>https://forum.netxms.org/post/9884https://forum.netxms.org/post/9884Sat, 09 Mar 2013 19:21:38 GMT<![CDATA[Reply to LOGWATCH: issues when parsing files with ISO-8859-1 encoding on Fri, 08 Mar 2013 20:52:00 GMT]]>Hi!

It's very strange, LOGWATCH should work with ISO-8859-1 without any problem. And file with only 123 as a content should be identical in both UTF-8 and ISO-8859-1 encodings. Can you post sample of matching and non-matching files?

Best regards,
Victor

]]>https://forum.netxms.org/post/9878https://forum.netxms.org/post/9878Fri, 08 Mar 2013 20:52:00 GMT