NagVis communicates with Shinken through the LiveStatus module. If you used the sample configuration, everything should be ready already. :)
You can review the configuration using the following steps.
The Livestatus API is server from the Shinken broker. It permits communications via TCP to efficiently retrieve the current state and performance data of supervised hosts and services from Shinken. It also exposes configuration information.
See enable Livestatus module.
Download the software and follow the installation guide from http://www.nagvis.org/
Nagvis needs to know where the Shinken Livestatus API is hosted.
In NagVis configuration file ‘’/etc/nagvis/nagvis.ini.php’‘:
[backend_live_1] backendtype="mklivestatus" htmlcgi="/nagios/cgi-bin" socket="tcp:localhost:50000"
If you are using a non local broker (or a distributed Shinken architecture with multiple brokers) you should change localhost to the IP/Servername/FQDN of your broker!