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. Integrate NetXMS with Check_MK for distributed monitoring solution

Integrate NetXMS with Check_MK for distributed monitoring solution

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 32.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.
  • J
    J
    ms.consultant
    wrote on last edited by
    #1

    Hello,

    for our NOC I want to propose to my manager NetXMS like Operations Manager with agents but for remote site I want to install Check_MK and integrate it with NetXMS via NetXMS-Agent.
    My questions:

    1. Is it possible to have this type of design NetXMS integrated with third party (Check_MK; Nagios; OpsView; etc...) ?

    2. NetXMS agent is able to collect all different data: (snmp traps; syslog, log files scan; schedule checks; scripts ouput value; threshold; etc..) ?

    3. can we use NetXMS server like collector at remote sites and forward the messages to the central NetXMS server due to assigned policies to the NetXMS agent at remote sites ?

    4. The Goal is to have a flexible design:
      NETWORK ELEMENTS (RTR; SW; VM; WCL; ...) <=> PROTOCOLS: (snmp; syslog; wmi; netflow; jflow; sflow; ....) <=> COLLECTOR (NetXMS-SRV; NetXMS-AGT or ThirdParty: Check_MK;...) <=> OPERATIONS MANAGER (NetXMS-SRV like OM or MoM)

    Thanks in advance
    Regards

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

      Hi!

      There are lot of different options for different integration scenarios. One option is to use event forwarding between NetXMS servers: collector server collects and analyzes data from devices, and send events to operations manager server when something happens. In such configuration historical data will be kept at collector server, but important events will be available on central server. If you prefer to use other collection tools, you can use integration utilities to send events and data to central NetXMS server (nxevent for sending events and nxpush for pushing performance data).
      NetXMS agent is able to parse log files and send events to server when match is found. It cannot forward SNMP traps. Agent is not collecting data automatically - only by server request.

      Best regards,
      Victor

      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