Keywords: Big Sister, Bigsister, Network Monitor, Network Monitoring, Perl, GPL, Big Brother, manual, SNMP

Network objects with simple names
Prev | Adding new hosts and services | Next

### Network objects with simple names

| Note
A resolvable name or an IP address (reverse lookup is not required) is a necessity for the agent (uxmon) to find the system on which the health checks need to be done. It is fundamental to understand that this name does not need to be identical with the name under which the data collected from this host is processed and grouped by the Big Sister server. In some cases it might be convenient to use the hostname for both the agent and the network object name in the Big Sister server. In other cases a somewhat finer granularity might be desired.

The syntax of the uxmon-net file is kept very simple: each entry starts with the name or IP address of the system to be monitored, followed by a list of health checks that should be applied to this system, e.g.:

`localhost type=ext2 diskfree`

will create a network object named like the output of `/bin/hostname` on the Big Sister server and run the diskfree test against all mounted partitions holding an ext2 file system of the local system. In the HTML status display on the server all test results will be grouped under the name of the network object. A working name resolution on the agent node, either through the `/etc/hosts` file or DNS, can be considered a prerequisite when using hostnames in the uxmon-net file.

| Warning
In the uxmon-net file either localhost or the output of /bin/hostname can be used to point checks to the local system. Unless no alias name (see section Network objects with alias names) is specified, the gathered data will be reported to a network object in the Big Sister server which has the system's hostname!

Prev | Up | Next
Adding new hosts and services | Home | Network objects with alias names