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:
Deployment Template | Elements | Minimum RAM | Minimum CPU Type | ||
---|---|---|---|---|---|
< 200 | 8 | Small | <100 | 2 GB | 2-core CPU |
Medium | 250–1000 | 16 GB | 6-core CPU | ||
Large | 1000+ | 32 GB | 12-core CPU | ||
4-cores/vCPUs | |||||
201 - 1000 | 32 GB | 8-cores/vCPUs | |||
1001 - 5000 | 128 GB | 24-cores/vCPUs |
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.
Each sizing example Each deployment template ensures the underlying configurations (for example, for the bundled MySQL database and JRE) match the likely resource demands to generate reports, dashboards, and perform queries. The following summarizes these configurations:
Configuration Parameter | Small | Medium | < 200 Elements | 201 - 1000 Elements | 1001 - 5000 ElementsLarge |
---|---|---|---|---|---|
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 | 100 | 150 | 250 | 500 | |
up.time Uptime Controller heap size | 512 768 MB | 1 GB | 1536 MB | 4096 MB2 GB |
Modifying the
...
Sizing Examples
After initial installation, if you need to accommodate a larger number of monitored Elements, you can manually change the deployment templates sizing examples using one of two methods:
...
Configuration Parameter | Configuration File and Location (relative to the up.time Uptime Infrastructure Monitor directory) | Parameter Name | Default Deployment 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= | 150 250 500 | ||
up.time Uptime Controller heap size | Linux: Windows: | Linux: Windows: | -Xmx512mXmx768m -Xmx1024mXmx1536m -Xmx2048mXmx4096m |
The recommended option to change a deployment template 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 deployment template sizing example in the least amount of steps.
Modifying Sample Templates
Update the DataStore configuration:
- Stop the DataStore service (uptime_datastore on Linux, or "up.time Uptime Data Store" on Windows)
- Move the the
ib_logfile0
and andib_logfile1
files files, found in the the<uptimeInstall>/datastore/data/
directory directory, to a backup location. - Back up the MySQL MySQL
my.ini
configuration configuration file, which is found in the the<uptimeInstall>/mysql/
directory directory. - Copy the the
<uptimeInstall>/sample/<size>/<os>/my.ini
template template file to the the<uptimeInstall>/mysql/
directory directory, replacing the existing one. - 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$
) 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:
- Back up the the
uptime.conf
file file, which is found in the the<uptimeInstall>/
directory directory. - Back up the Data Collector configuration file (
uptime.jcnf
on on Linux, or orUptimeDataCollector.ini
on on Windows), which is found in the the<uptimeInstall>/
directory directory. - Copy the the
uptime.conf
, and anduptime.jcnf
or orUptimeDataCollector.ini
files 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 up.time Uptime Infrastructure Monitor deployment (for example, the the$MS_STRING_FS$
classpath classpath variable, and and$DATASTORE_HOST$
). - 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:
- 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
- Linux: the the
- Copy the the
start.sh
or orUptimeController.ini
file 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 up.time Uptime Infrastructure Monitor deployment. - 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:
- Back up the the
php.ini
up.time Uptime Web server configuration file, which is found in the the<uptimeInstall>/apache/conf/
directory directory. - 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. - 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$
). - Restart the up.time Uptime Web server (uptime_httpd on Linux, or "up.time Uptime Web Server" on Windows).
...