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. Syslog monitoring

Syslog monitoring

Scheduled Pinned Locked Moved Support
8 Posts 4 Posters 40.4k 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.
  • M
    M
    Mr_Mitch
    wrote on last edited by
    #1

    Hello everybody,

    I have a program that can create a log whenever i want.
    What i want is that the logs are going to the Syslog of NetXMS.

    I have already changed the EnableSyslogDaemon to 1. However i don't know what to do next.
    I don't know if Syslog is suppose to show me logs of windows or something already (Because it does not). And i don't know how to show the created logs in Syslog.

    Sorry for the Amateur post. But i don't know how to explain this good haha
    In the attachment you will see what i get right now, while watching Syslog.


    lala.png

    1 Reply Last reply
    0
    • T
      T
      tomaskir
      wrote on last edited by
      #2

      I suggest reading up on what Syslog is here http://www.networkmanagementsoftware.com/what-is-syslog

      On Windows, system logs will not automatically be delivered to the NetXMS Syslog server.
      (not on any OS/device for that matter, it needs configuration)

      Probably what you want to look at is the LogWatch SubAgent, documentation is here:
      https://wiki.netxms.org/wiki/UM:Log_Monitoring

      1 Reply Last reply
      0
      • M
        M
        Mr_Mitch
        wrote on last edited by
        #3

        @tomaskir said in Syslog monitoring:

        I suggest reading up on what Syslog is here http://www.networkmanagementsoftware.com/what-is-syslog

        On Windows, system logs will not automatically be delivered to the NetXMS Syslog server.
        (not on any OS/device for that matter, it needs configuration)

        Probably what you want to look at is the LogWatch SubAgent, documentation is here:
        https://wiki.netxms.org/wiki/UM:Log_Monitoring

        Thanks for responding, However i already read those documents. And then i see this:

        NetXMS has built-in syslog server, which can be used to receive logs from network devices and servers. It is also possible to parse incoming syslog messages in a way similar to Windows Event Log monitoring. To parse syslog messages, LOGWATCH subagent is not needed – parsing is done by the server itself. You should only create parser configuration file for syslog in console via Control Panel – Syslog Parser.

        So i don't need to use anything of subagent? However, how do i do it then?

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

          Hi,

          you don't need logwatch subagent if you receiving and parsing syslog records - but then you have to configure your application to use syslog protocol for logging instead of just writing log file. Or, you should have something that picks up application log file and sends it using syslog protocol to NetXMS server.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • M
            M
            Mr_Mitch
            wrote on last edited by
            #5

            @victor said in Syslog monitoring:

            Hi,

            you don't need logwatch subagent if you receiving and parsing syslog records - but then you have to configure your application to use syslog protocol for logging instead of just writing log file. Or, you should have something that picks up application log file and sends it using syslog protocol to NetXMS server.

            Best regards,
            Victor

            Sorry for the late response.

            I think i get it, and will try a few things. If i can't figure it out, il post it again haha

            1 Reply Last reply
            0
            • M
              M
              Mr_Mitch
              wrote on last edited by
              #6

              @mr_mitch said in Syslog monitoring:

              @victor said in Syslog monitoring:

              Hi,

              you don't need logwatch subagent if you receiving and parsing syslog records - but then you have to configure your application to use syslog protocol for logging instead of just writing log file. Or, you should have something that picks up application log file and sends it using syslog protocol to NetXMS server.

              Best regards,
              Victor

              Sorry for the late response.

              I think i get it, and will try a few things. If i can't figure it out, il post it again haha

              Okay, i'm not getting it...

              The code for the whole log test = http://pastebin.com/ks5i5XC3

              This file needs to send his logs to the Syslog server of NetXMS.
              However, every time when i edit something. The application breaks...

              1 Reply Last reply
              0
              • A
                A
                Alex Kirhenshtein
                wrote on last edited by
                #7

                I'm not familiar with NLog, but it looks like syslog target is not used (single logger in rules, with writeTo=fileTarget).
                Also you need to configure syslog target (according to https://github.com/graffen/NLog.Targets.Syslog😞

                  <targets>
                    <target name="syslog" type="Syslog" syslogserver="127.0.0.1" port="514" facility="Local7" sender="MyProgram" layout="[CustomPrefix] ${machinename} ${message}" />
                  </targets>
                
                1 Reply Last reply
                0
                • M
                  M
                  Mr_Mitch
                  wrote on last edited by
                  #8

                  @alk said in Syslog monitoring:

                  I'm not familiar with NLog, but it looks like syslog target is not used (single logger in rules, with writeTo=fileTarget).
                  Also you need to configure syslog target (according to https://github.com/graffen/NLog.Targets.Syslog😞

                    <targets>
                      <target name="syslog" type="Syslog" syslogserver="127.0.0.1" port="514" facility="Local7" sender="MyProgram" layout="[CustomPrefix] ${machinename} ${message}" />
                    </targets>
                  

                  sorry for the verryyy late response xD

                  However, Changing the target type to syslog. Make the application not to start at all 😕

                  I have tryed alot of methods. but they are not working.

                  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