up.time includes user-definable parameters that can control some aspects of its behavior including the following:

  • Database Settings
  • Mail Server Settings
  • Global Scan threshold settings
  • Resource Scan threshold settings
  • Proxy settings
  • Remote reporting settings
  • RSS feed settings
  • Splunk integration settings
  • Web monitor settings

From a configuration perspective, there are two types of parameters:

  • parameters whose modification does not require a restart of the Core service (also known as the up.time Data Collector service); these parameters can be modified in up.time, on the Config panel
  • parameters whose modification requires a restart of the Core service; these parameters are found in the uptime.conf file

Modifying up.time Config Panel Settings

Configuration parameters that are not directly tied to, thus do not require a restart of, the up.time Core service can be modified directly in the up.time GUI:

In general, to edit these configuration settings in the up.time interface, do the following:

  1. On the up.time tool bar, click Config.
  2. In the left pane, click up.time Configuration.
  3. Enter the configuration variable and new value.
  4. Click Update to save your changes.

Only the variables whose default values have been modified appear in the up.time Configuration panel.

Topics on this page
See the following topics for more information

Modifying uptime.conf File Settings

Configuration parameters that are directly tied to the up.time Core service are found in the uptime.conf file. uptime.conf is a text file that you can modify in any text editor, and can be found in the root up.time installation directory.

In addition to the up.time database, uptime.conf parameters affect a variety of up.time behavior.

Not all of the settings listed in this section will necessarily be found in your particular uptime.conf file.

 

Stopping and Restarting up.time Services

In addition to the Web interface, the up.time Monitoring Station consists of the following services:

  • DataStore
  • Web server
  • Data Collector (also called the Core)
  • Controller

These services run in the background and start automatically after the operating system on the server hosting up.time starts. However, system administrators may need to stop the up.time services (for example, before making configuration changes to the uptime.conf file, performing an upgrade, or archiving the DataStore).

Stopping the up.time Services

To stop the up.time services in Windows, do the following:

  1. Open the Services Control Panel.
  2. Find the following entries, and for each, Stop the service:
    • up.time Controller
    • up.time Web Server
    • up.time Data Collector
    • up.time Data Store

To stop the up.time services on Linux, do the following:

  1. Log into the Monitoring Station as user root.
  2. Type the following command to stop the Controller:
    /etc/init.d/uptime_controller stop
  3. Type the following command to stop the Web server:
    /etc/init.d/uptime_httpd stop
  4. Type the following command to stop the Data Collector:
    /etc/init.d/uptime_core stop
  5. Type the following command to stop the DataStore:
    /etc/init.d/uptime_datastore stop
Starting the up.time Services

To restart the up.time services in Windows, do the following:

  1. Open the Services Control Panel.
  2. Find the following entries, and for each, Start the service:
    • up.time Data Store
    • up.time Data Collector
    • up.time Web Server
    • up.time Controller

To restart the up.time services on Linux, do the following:

  1. At the command line, log into the Monitoring Station as user root.
  2. Type the following command to start the DataStore:
    /etc/init.d/uptime_datastore start
  3. Type the following command to start the Data Collector:
    /etc/init.d/uptime_core start
  4. Type the following command to start the Web server:
    /etc/init.d/uptime_httpd start
    Type the following command to stop the Controller:
    /etc/init.d/uptime_controller start

 

  • No labels