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. Event Log parsing

Event Log parsing

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 45.3k 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.
  • I
    I
    iliecz
    wrote on last edited by
    #1

    I am trying to parse the windows application event log to look for sql agent jobs failures.
    I want the full windows event log text sent over email since there can be a lot of job fails.

    Agent parse file configuration looks like this

    <parser>
      <file>*Application</file>
      <rules>
        <rule>
          <severity>6</severity>
          <match>(SQL Server Scheduled Job)*(Message: The job failed)*</match>
          <event params="1">100025</event>
        </rule>
      </rules>
    </parser>
    If I let it configured like this it will only send some generic information.
    If I replace <match>(.*)</match> it will send the full event text.
    In both situation it will send the message twice.
    What am I doing wrong?

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

      Hi!

      It probably should be something like this:

      <match>(SQL Server Scheduled Job.*Message: The job failed.*)</match>

      if you want to capture full text but match only messages with certain words in it.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • I
        I
        iliecz
        wrote on last edited by
        #3

        Thanks, it worked!
        Now I have another issue with establishing a counter for the matched records and displayed in a dashboard.
        I think the parameter I need is LogWatch.Parser.MatchedRecords(*) .
        Simply placing this parameter in Data Collection Configuration dose not work
        What do I need to replace * with in order to run correctly?

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

          Hi!

          You should replace * with parser's name. By default parser name is file name (given in <file>), but you can override it with name attribute, like this:

          <parser name="AppLog">
            <file>*Application</file>
            <rules>
              <rule>
                <severity>6</severity>
                <match>(SQL Server Scheduled Job)*(Message: The job failed)*</match>
                <event params="1">100025</event>
              </rule>
            </rules>
          </parser>

          and then use LogWatch.Parser.MatchedRecords(AppLog)

          Best regards,
          Victor

          1 Reply Last reply
          0
          • I
            I
            iliecz
            wrote on last edited by
            #5

            Once again thanks a lot.
            It's working like a charm.

            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