In this recipe, you'll learn how to use authenticated contacts to refine our control of access to information in the Nagios Core web interface. This recipe is useful in situations where a particular user requires information on the status of certain hosts and services but should not be allowed to view others. This is a setup that can't be managed with the directives in cgi.cfg
.
As a simple example, on a given monitoring server, we might have two hosts configured as follows:
define host { use linux-server host_name sparta.example.net alias sparta address 192.0.2.21 contacts nagiosadmin } define host { use linux-server host_name athens.example.net alias athens address 192.0.2.22 contacts nagiosadmin }
We might like to add a new user athensadmin
with permissions to view the status of and run commands on the athens.example.net
host and its services but not the sparta.example.net
host or its...