Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. LOGWATCH: issues when parsing files with ISO-8859-1 encoding

LOGWATCH: issues when parsing files with ISO-8859-1 encoding

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 13.9k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    J
    Jos.Verduijn
    wrote on last edited by
    #1

    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

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      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

      1 Reply Last reply
      0
      • J
        J
        Jos.Verduijn
        wrote on last edited by
        #3

        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

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups