Page History

Sizing varies based on the number of monitors per element, the type of objects monitored, and the method used to gather performance data.

...

  Uptime Infrastructure Monitor recommendations are based on an average of 2 or 3 monitors per element.

...

During Uptime Infrastructure Monitor's installation, one of three options was selected depending on the size of your monitored environment. The choice determined how certain resources were allocated, and subsequent hardware requirements:

As a general rule of thumb when planning the allocated disk space, you should plan on allocating about 4 GB per monitored element. Note that per element usages are per year, unless you archive using old data.

...

Modifying the Sizing Examples

After initial installation, if you need to accommodate a larger number of monitored Elements, you can manually change the sizing examples using one of two methods: 

...

The recommended option to change a sizing example is to use the sample configuration files that are found in the the <uptimeInstall>/sample directory  directory as a starting point. This option moves you to a different sizing example in the least amount of steps.

Modifying Sample Templates

Update the DataStore configuration:

1. Stop the DataStore service (uptime_datastore on Linux, or "up.time Uptime Data Store" on Windows)
2. Move the the ib_logfile0 and  and ib_logfile1 files files, found in the the <uptimeInstall>/datastore/data/ directory directory, to a backup location.
3. Back up the MySQL MySQL my.ini configuration  configuration file, which is found in the the <uptimeInstall>/mysql/ directory directory.
4. Copy the the <uptimeInstall>/sample/<size>/<os>/my.ini template  template file to the the <uptimeInstall>/mysql/ directory directory, replacing the existing one.
5. Edit the the my.ini file file, replacing all all $VARIABLE$ instances  instances with values that match your up.time Uptime Infrastructure Monitor deployment (for example, $DATASTORE_PORT$ and  and $USER_INSTALL_DIR$)

6. Start the DataStore service
   You can confirm the change was successful by referring to the the <uptimeInstall>/datastore/data/<hostname>.err log log. Look for output similar to the following:

   Code Block

   140110 14:26:28 InnoDB: Initializing buffer pool, size = 23.0G 140110 14:26:29 InnoDB: Completed initialization of buffer pool 140110 14:26:29 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 512768 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 500 600 700 140110 14:26:33 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 512768 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 500 600 700

Update the up.time Uptime Data Collector configuration:

1. Back up the the uptime.conf file file, which is found in the the <uptimeInstall>/ directory directory.
2. Back up the Data Collector configuration file (uptime.jcnf on  on Linux, or or UptimeDataCollector.ini on  on Windows), which is found in the the <uptimeInstall>/ directory directory.
3. Copy the the uptime.conf, and and uptime.jcnf or  or UptimeDataCollector.ini files  files from the the <uptimeInstall>/sample/<size>/<os>/ directories  directories to the the <uptimeInstall>/ directory directory, replacing the existing ones.
4. Edit both files, replacing all all $VARIABLE$ instances  instances with values that match your up.time Uptime Infrastructure Monitor deployment (for example, the the $MS_STRING_FS$ classpath  classpath variable, and and $DATASTORE_HOST$).
5. Restart the up.time Uptime data-collection service (uptime_core on Linux, or "up.time Uptime Data Collector" on Windows)

Update the up.time Uptime Controller configuration:

1. Back up the up.time Uptime Controller configuration file:
   • Linux: the the start.sh script script, which is found in the the <uptimeInstall>/controller/service/ directory directory
   • Windows: the the UptimeController.ini configuration  configuration file, which is found in the the <uptimeInstall>\controller\service directory directory
2. Copy the the start.sh or  or UptimeController.ini file  file from the the <uptimeInstall>/sample/<size>/<os>/ directory  directory to the the <uptimeInstall>/controller/service/ directory directory, replacing the existing one.
3. Edit the file, replacing all all $VARIABLE$ instances  instances with values that match your up.time Uptime Infrastructure Monitor deployment.
4. Restart the up.time Uptime Controller service (uptime_controller on Linux, or up.time Uptime Controller on Windows)

Update the up.time Uptime Web server:

1. Back up the the php.ini up.time  Uptime Web server configuration file, which is found in the the <uptimeInstall>/apache/conf/ directory directory.
2. Copy the the php.ini file  file from the the <uptimeInstall>/sample/<size>/<os>/ directory  directory to the the <uptimeInstall>/apache/conf/ directory directory, replacing the existing one.
3. Edit the file, replacing all all $VARIABLE$ instances  instances with values that match your up.time Uptime Infrastructure Monitor deployment (for example, $USER_INSTALL_DIR$).
4. Restart the up.time Uptime Web server (uptime_httpd on Linux, or "up.time Uptime Web Server" on Windows).