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

F

farcsa

@farcsa
Unfollow Follow
About
Posts
5
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Windows Event Log parser
    F farcsa
    Support

    Excuse me, but my above problem is outstanding. Could anybody help me to resolve this?


  • Windows Event Log parser
    F farcsa
    Support

    In the documentation there are these "levels":
    1 Error
    2 Warning
    4 Information
    8 Audit Success
    16 Audit Failure
    These levels are in Windows XP.

    But there isn't Critical, like in Windows 7 and above versions. As I wrote, in Windows 7 (and above) the levels are:
    1 Critical
    2 Error
    3 Warning
    4 Information

    So, how to combine the NetXMS levels for capturing Windows Critical level events?

    To help clarify my problem, I insert the link of TechNet documentation about Windows Event Properties:
    http://technet.microsoft.com/en-us/library/cc765981.aspx

    Thanks for your answers!


  • Windows Event Log parser
    F farcsa
    Support

    Hi!
    I have 3 questions.
    I have a parser file hereunder:

    <parser>
      <file>*Application</file>
      <rules>
        <rule>
          <match>(.*)</match>
          <id>5</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <id>1006</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <id>1008</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <id>1023</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <id>1057</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <id>12014</id>
        </rule>
        <rule>
          <match>(.*)</match>
          <level>1</level>
          <event params="1">100003</event>
        </rule>
      </rules>
    </parser>

    1:
    Is there a simpler method to exclude events with predefined event id? (e.g.: 5,1006,1008,...)

    2:
    I manage Windows 7, Windows Server 2008 and Windows Server 2012, and i see that the severity levels are the following:
    Critical =1
    Error=2
    Warning =3
    Information=4

    The above example captures only Windows error level events. How to set the <level> parameter to capture Windows critical events? (And, of course, how to combine the values?)

    3:
    With the above parser, the agent always misses the event with event id 1. What could be the reason?


  • Integration with LDAP question
    F farcsa
    Support

    I am also having issues trying to authenticating AD users via LDAP. The log file contains that line:
    "LDAPConnection::syncUsers(): FAILED - server was compiled without LDAP support"

    How to compile NetXMS with LDAP support?


  • NetXMS Objects Decorator unexpectedly and randomly turns off
    F farcsa
    Support

    An annoying bug in NetXMS Management Console (1.2.16): the NetXMS Objects Decorator unexpectedly and randomly turns off, and the statuses in the Object tree disappear. (my environment: Windows 7, Java 7).

  • 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