Icinga2 and NagVis integration

This forum was archived to /woltlab and is now in read-only mode.
  • Hey all,

    I can't seem to find much documentation/information about setting up NagVis with Icinga2. I know it's possible, yet I do not know how to do it. I've found various other older threads about this but they are irrelevant now because most point to broken links and outdated documentation.

    Here's where I am at during the installation process:

    - I have everything on this system requirements page from NagVis, but am stuck on the installation of Livestatus.


    I'm trying to follow this guide, but it only shows how to configure it for Nagios (not Icinga2) and I do not know how to "load livestatus.o into Icinga2".

    Could anybody help me out?


  • Wolfgang

    Yes, I've enabled the "livestatus" feature into Icinga2, but this does not generate a "socket file" as described by the guide that I linked before (or does it?).

    Here's the part of the guide that I am confused about:

    I assume that I'm not supposed to load it into Nagios, but rather Icinga2. How do you do this?


    From the second link you provided, I must specify the socket file that I mentioned in that file, so I cannot continue with that part until I generate it.

  • livestatus is an icinga2 module.

    Simply do an icinga2 feature enable livestatus and restart icinga2.

    After that you have a socket below /var/run/icinga2/cmd, called "livestatus".

    That socket has to be configured in /usr/share/nagvis/etc/nagvis.ini, mine looks like:

    1. [backend_live_1]
    2. backendtype="mklivestatus"
    3. socket="unix:/var/run/icinga2/cmd/livestatus"
  • sru

    Cool, thanks!

    I was unaware that the command generated the socket file.

    Installation Notes (perhaps this will help somebody else):

    Options that I chose while running ./install-sh -s icinga2

    - Specify the icinga2 base directory as /usr/share/icinga2

    - Set the NagVis base to /usr/share/nagvis

    - Confirmed use of backend mklivestatus

    - Set the NagVis web path to /nagvis

    - Set web-server user to apache

    - Set web-server group to apache

    - Confirmed creation of Apache config file

    I was then able to access the web interface at http://server-ip/nagvis

    Thanks to Wolfgang and sru for the help!

    Thread is now resolved.