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. Log Scrapping / Log Watch - Multiple Alerts

Log Scrapping / Log Watch - Multiple Alerts

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 25.2k 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.
  • T
    T
    TICK_TEL
    wrote on last edited by
    #1

    We are using the log watch feature to monitor the logs of our Interfaces in different file paths etc.

    Do within the nxagentd.conf file we are doing;

    [LOGWATCH]
    Parser = C:\NetXMS\etc\interface1.xml
    Parser = C:\NetXMS\etc\interface2.xml
    

    Then within Interface1.xml we are doing;

    <parser>
      <file>C:\inetpub\Interface1\logs\Log_%Y_%m_%d.txt</file>
      <rules>
        <rule>
          <match>Error(.*)</match>
          <event>100050</event>
        </rule>
      </rules>
    </parser>
    

    The trouble we are having is both Interface 1, 2 etc use the same event to fire on in NetXMS. Ideally we'd like to stick to the one event but be able to identify which interface/log directory has fired it.

    Is it possible to add something to the XMLS for us to be able to tell which Interface has fired the error? I.e. Interface 1 or Interface 2 using the same event? Or do we need to setup separate events for each one?

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

      Hi,

      currently it's not possible. I've added feature request for ability to pass extra parameters to generated event: https://track.radensolutions.com/issue/NX-1643

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        TICK_TEL
        wrote on last edited by
        #3

        Thanks Victor. That would be really handy.

        Any ideas of an ETA.

        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