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

T

Tomaric

@Tomaric
Unfollow Follow
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Windows Event Log parser file not filtering
    T Tomaric
    Support

    Curious. I have these parser file.

    <parser>
      <file>*Application</file>
      <rules>
        <rule>
          <Level>1</Level>
          <match>(.*)</match>
          <event params="1">100804</event>
        </rule>
         
        <rule>
          <Level>2</Level>
          <match>(.*)</match>
          <event params="1">100803</event>
        </rule>
      </rules>
    </parser>

    The idea is if there are a error or warning in Windows application log file to send an email. The only issue is it sends every event, the parser does not filter. Is my format incorrect in the parser file? I've tried using both <level> and <severity>

    One issue here is since the filter does not filter "information" logs once I turn this filter and alerts on NetXMS goes into a continuous loop of alerts and emails. Kind of a show stopper.

    Thanks

  • 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