## Creating HTML Pages From The Configuration Data

A Note About Creating HTML Pages

This step is optional and may be skipped if you do not want to generate HTML files for use with the web interface. Also, if you have enabled the auto_generate_html option in the main configuration file, NetSaint will automatically recreate HTML files in the location you specified when it starts, so you don't need to do this manually. Creating the HTML files manually from the command line is good to do when you first start using NetSaint, as it may reveal problems that would prevent monitoring from working properly.

Creating HTML Pages From The Command Line

In order to create the HTML pages from the command line, you must invoke NetSaint with the -h option as follows...

Exmaple: ./netsaint -h <main_config_file>

Note that you must specify the path/filename of your main configuration file on the command line and not your host configuration file. All HTML files will be generated in the current working directory. A description of these files is given below.

The HTML Files

This is a list of the different HTML files that NetSaint will create from your configuration data...

File | Contents
contacts.html | Information on all contacts (name, alias, email address, notification options, notification commands, etc.)
contactgroups.html | Information on all contact groups (group name, contact members, etc.)
hosts.html | Information on all hosts (name, address, router address, etc.)
hostgroups.html | Information on all host groups (group name, contact group, host members, etc.)
commands.html | Information on all commands used to check the status of hosts/services and notify contacts
services.html | Information on all services that are being monitored (service name, host name, check command, max. retries, notification options, etc.)
timeperiods.html | Information on all time periods that you have defined for use with notifications and service checks

After You've Created The HTML Pages

After the HTML pages have been generated and you are happy with them, you will need to move them to the proper directory so they can be accessed via the web. The logical choice would be to move them into the same directory that contains the main HTML files. For example, if you main HTML files are located in the /usr/local/netsaint/share directory, you would use the following command...

mv *.html /usr/local/netsaint/share

The main reason for moving the HTML files into this directory is that the links on the CGI generated pages will (by default) expect them there. This can be changed by using special option to the configure script, but I won't go into that here.

Where To Go From Here

The next logical step you should take is to fire up NetSaint and start the monitoring process. Documentation on doing this can be found here.