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 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:
...
| Configuration Parameter | < 200 Elements | 201 - 1000 Elements | 1001 - 5000 Elements | |
|---|---|---|---|---|
| MySQL buffer pool size | 120 180 MB | 2 3 GB | 4 8 GB | |
| MySQL log file size | 20 30 MB | 512 768 MB | 1 2 GB | |
| MySQL maximum open connections | 151201 | 301 | 551 | |
| Java heap size | 1 2 GB2 | 4 GB4 | 8 GB | |
| service threads | 5075 | 100150 | 200300 | |
| Data Collector maximum open connections | 100150 | 250 | 500 | |
| Uptime Controller heap size | 512 768 MB | 1 GB | 1536 MB | 4096 MB2 GB |
Modifying the Sizing Examples
...
| Configuration Parameter | Configuration File and Location (relative to the Uptime Infrastructure Monitor directory) | Parameter Name | Default Sizing Values | ||
|---|---|---|---|---|---|
| MySQL buffer pool size | /mysql/my.ini | innodb_buffer_pool_size= |
| ||
| MySQL log file size | /mysql/my.ini | innodb_log_file_size= | 30M 20M 512M 768M 1G 2G | ||
| MySQL maximum open connections | /mysql/my.ini | max_connections= | 201 301 551 | ||
| Java heap size | Linux: Windows: | Linux: Windows: | Linux: | Windows: | |
| service threads | /uptime.conf | serviceThreads= | 75 50 100 150 200 300 | ||
| Data Collector maximum open connections | /uptime.conf | connectionPoolMaximum= | 150250500 | ||
| Uptime Controller heap size | Linux: Windows: | Linux: Windows: | -Xmx512mXmx768m-Xmx1024mXmx1536m-Xmx2048mXmx4096m | ||
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.
...
- Stop the DataStore service (uptime_datastore on Linux, or "Uptime Data Store" on Windows)
- Move the the
ib_logfile0and andib_logfile1files files, found in the the<uptimeInstall>/datastore/data/directory directory, to a backup location. - Back up the MySQL MySQL
my.iniconfiguration configuration file, which is found in the the<uptimeInstall>/mysql/directory directory. - Copy the the
<uptimeInstall>/sample/<size>/<os>/my.initemplate template file to the the<uptimeInstall>/mysql/directory directory, replacing the existing one. - Edit the the
my.inifile file, replacing all all$VARIABLE$instances instances with values that match your Uptime Infrastructure Monitor deployment (for example,$DATASTORE_PORT$and and$USER_INSTALL_DIR$) Start the DataStore service
You can confirm the change was successful by referring to the the<uptimeInstall>/datastore/data/<hostname>.errlog 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 Uptime Data Collector configuration:
- Back up the the
uptime.conffile file, which is found in the the<uptimeInstall>/directory directory. - Back up the Data Collector configuration file (
uptime.jcnfon on Linux, or orUptimeDataCollector.inion on Windows), which is found in the the<uptimeInstall>/directory directory. - Copy the the
uptime.conf, and anduptime.jcnfor orUptimeDataCollector.inifiles files from the the<uptimeInstall>/sample/<size>/<os>/directories directories to the the<uptimeInstall>/directory directory, replacing the existing ones. - Edit both files, replacing all all
$VARIABLE$instances instances with values that match your Uptime Infrastructure Monitor deployment (for example, the the$MS_STRING_FS$classpath classpath variable, and and$DATASTORE_HOST$). - Restart the Uptime data-collection service (uptime_core on Linux, or "Uptime Data Collector" on Windows)
...
- Back up the Uptime Controller configuration file:
- Linux: the the
start.shscript script, which is found in the the<uptimeInstall>/controller/service/directory directory - Windows: the the
UptimeController.iniconfiguration configuration file, which is found in the the<uptimeInstall>\controller\servicedirectory directory
- Linux: the the
- Copy the the
start.shor orUptimeController.inifile file from the the<uptimeInstall>/sample/<size>/<os>/directory directory to the the<uptimeInstall>/controller/service/directory directory, replacing the existing one. - Edit the file, replacing all all
$VARIABLE$instances instances with values that match your Uptime Infrastructure Monitor deployment. - Restart the Uptime Controller service (uptime_controller on Linux, or Uptime Controller on Windows)
Update the Uptime Web server:
- Back up the the
php.iniUptime Uptime Web server configuration file, which is found in the the<uptimeInstall>/apache/conf/directory directory. - Copy the the
php.inifile file from the the<uptimeInstall>/sample/<size>/<os>/directory directory to the the<uptimeInstall>/apache/conf/directory directory, replacing the existing one. - Edit the file, replacing all all
$VARIABLE$instances instances with values that match your Uptime Infrastructure Monitor deployment (for example,$USER_INSTALL_DIR$). - Restart the Uptime Web server (uptime_httpd on Linux, or "Uptime Web Server" on Windows).