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. Events from syslog parser generated twice

Events from syslog parser generated twice

Scheduled Pinned Locked Moved Support
8 Posts 2 Posters 49.5k 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.
  • Dani@M3TU
    Dani@M3TU
    Dani@M3T
    wrote on last edited by
    #1

    I just started with syslog parser for the first time. At the moment I only have 3 rules to start:

    <parser>
      <rules>
          <rule>
            <match>.*Due to active connection allowed exceeded.*</match>
            <event params="0">100832</event>
          </rule>
          <rule>
            <match>.*msg=(Administrator|User) (.*) from l2tp has logged in ZyWALL.*</match>
            <event params="2">100833</event>
          </rule>
          <rule>
            <match>.*msg=(Administrator|User) (.*) from l2tp has logged out ZyWALL.*</match>
            <event params="2">100834</event>
          </rule>
      </rules>
      <macros/>
    </parser>

    The first is ok.
    But the 2. and the 3. are always generated twice. But in internal syslog there is only one entry. (see attachments)
    My install is V1.2.11 (from sources) on linux.
    Thanks for any help.


    syslog.png

    events.png

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

      Looks strange. I'll try your policy on my test system later today.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • Dani@M3TU
        Dani@M3TU
        Dani@M3T
        wrote on last edited by
        #3

        Hi Victor

        Thanks a lot. It looks strange for me too. No hurry in this case 😉

        Dani

        1 Reply Last reply
        0
        • Dani@M3TU
          Dani@M3TU
          Dani@M3T
          wrote on last edited by
          #4

          I have a follow up to this case.
          I retested the same situation and double checked it in syslog and in internal log of the node. Now I see the log entries also twice (I don't drink anything  ;).
          So they are generated twice by the original device. Definetively not a NetXMS fault. I don't understand why I saw this log entries only once yesterday (as you can see in the printscreen at the original post).....

          Does someone has an idea for the log parser to only generate one event altough there are double entries in syslog?

          thanks, Dani


          syslog.png

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

            You cannot suppress second event from log parser but you can handle duplicate event differently. For example, you can set some custom attribute to the time stamp of received event, and ignore all next events if they are within certain time frame. Actual solution depends on how you are using those events.

            Best regards,
            Victor

            1 Reply Last reply
            0
            • Dani@M3TU
              Dani@M3TU
              Dani@M3T
              wrote on last edited by
              #6

              So I have to find a solution on level of events and not in the syslog parser. Is that what you mean?

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

                Yes, exactly. I can possibly suggest some if you tell me how you want to use those events.

                Best regards,
                Victor

                1 Reply Last reply
                0
                • Dani@M3TU
                  Dani@M3TU
                  Dani@M3T
                  wrote on last edited by
                  #8

                  Hi Victor

                  Thanks a lot. Thats ok for the moment  🙂

                  thanks, Dani

                  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