Monitoring Server

Generally there will only be one monitoring server on your network. It is the server responsible for checking all of the other servers, pulling data off the network in various ways, and issuing all of your notifications and alerts. It is also the most complicated type of State server to install.

State

If you have all of the proper dependencies, then running the standard autoconf procedure should work fine for installing State as a monitoring server. Note that you need to make sure PostgreSQL is installed, otherwise State will assume that it is running as a statistics server with no database support. Otherwise, just go through the standard steps:

$ cd STATE_SOURCE_DIRECTORY
$ ./configure
$ make
$ make install
      

By default, State will create and use a database with the name state. If you'd like to change this, use the --with-database-name configure option. If you, at anytime, would like to avoid building any libraries you may have placed in the State source directory, such as the Apache Portable Runtime, then you can use the state target in the Makefile to rebuild:

$ make state
      

This only builds State specific targets, no third party libraries or tools. After State is installed, you can setup the database State will be using.

PostgreSQL

Now that State is installed you'll need to setup your PostgreSQL database for storing the runtime information and running the PHP website. You can't run State until this is done. You'll need to choose your database name now, and the machine that you'd like to place the database on. It's suggested that you run PostgreSQL on the same machine as State, for performance reasons, although that isn't entirely necessary.

$ cd STATE_SOURCE_DIRECTORY
$ make database
      

After running this, there will be a PostgreSQL database with the name given during the configuration step and populated with the base schema. Now you can move on to the configuration step.