Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Elements201 - 1000 Elements1001 - 5000 Elements
MySQL buffer pool size120 180 MB2 3 GB4 8 GB
MySQL log file size20 30 MB512 768 MB1 2 GB
MySQL maximum open connections151201301551
Java heap size1 GB2 GB4 GB8 GB
service threads5075100150200300
Data Collector maximum open connections100150250500
Uptime Controller heap size512 768 MB1 GB2 GB1536 MB4096 MB

Modifying the Sizing Examples

...

Configuration ParameterConfiguration File and Location
(relative to the Uptime Infrastructure Monitor  directory)
Parameter Name

Default Sizing Values
(< 200, 201 - 1000,
1001 - 5000)

MySQL buffer pool size/mysql/my.iniinnodb_buffer_pool_size=

120M 180M
2G 3G
4G 8G

MySQL log file size/mysql/my.iniinnodb_log_file_size=20M 30M
512M 768M
1G 2G
MySQL maximum open connections/mysql/my.inimax_connections=151
201
301
551
Java heap size

Linux:
/uptime.jncf

Windows:
\UptimeDataCollector.ini

Linux:
-Xmx<size>

Windows:
vm.heapsize.preferred=

Linux:
-Xmx1G -Xmx2G
-Xmx4G
-Xmx8G

Windows:
1024m
2048m
4096m -2 GB
-4 GB
-8 GB

service threads/uptime.confserviceThreads=50 75
100 150
200 300
Data Collector maximum open connections/uptime.confconnectionPoolMaximum=100
150
250
500
Uptime Controller heap size

Linux:
/controller/service/start.sh

Windows:
\controller\service\UptimeController.ini

Linux:
-Xmx<size>

Windows:
vmarg.2=

-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.

...

  1. Stop the DataStore service (uptime_datastore on Linux, or "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 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 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 Uptime Infrastructure Monitor deployment (for example, the the $MS_STRING_FS$ classpath  classpath variable, and and $DATASTORE_HOST$).
  5. Restart the Uptime data-collection service (uptime_core on Linux, or "Uptime Data Collector" on Windows)

...

  1. Back up the 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 Uptime Infrastructure Monitor deployment.
  4. Restart the Uptime Controller service (uptime_controller on Linux, or Uptime Controller on Windows)

Update the Uptime Web server:

  1. Back up the the php.ini Uptime  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 Uptime Infrastructure Monitor deployment (for example, $USER_INSTALL_DIR$).
  4. Restart the Uptime Web server (uptime_httpd on Linux, or "Uptime Web Server" on Windows).