This article describes how to adjust the thresholds that are used to determine coloring within the Global Scan performance fields for all elements or for individual elements.
Understanding What Each Field Represents
Before you change GlobalScan thresholds, refer to the table below for a description of each field that you can control and the associated setting name that will be used later in this article.
|Performance Field||Description||DataStore setting name||uptime.conf setting name|
|TOT||The overall total CPU % busy.||gs_cpu_warn|
|% Used||The capacity of the file system that is most full on the element.||gs_diskfull_warn|
|% Busy||The work time of the busiest spindle on the element.||gs_diskbusy_warn|
|Swap Used||Total swap space used.||gs_swap_warn|
Each field has two setting names: one to control the warning (yellow) threshold and another to set the critical (red) threshold. Either or both settings can be modified. The setting to update for warning thresholds includes the word warn in the setting and the critical threshold setting includes the word crit in the setting name.
Changing Thresholds for all Elements
To change the current thresholds for all elements within your up.time installation, complete the following steps:
Connect to your up.time DataStore using an ODBC or database tool. Assuming that you have installed up.time in the default location, you can access the DataStore at the command line using the following commands:
«change to the up.time installation directory» cd mysql cd bin ./mysql -u uptime --password=uptime -P 3308 --protocol=TCP uptime
After you login to the up.time DataStore, run a command to update the threshold that you want to use with all elements. The command format and an example are detailed below. Replace the «field» text in the example below with a value from the DataStore setting name column in the table above. Replace the «new value» text in the example below with your new threshold setting (decimal values are not permitted for thresholds).
|All mysql commands assume that you are using a MySQL DataStore. The format of the commands may differ slightly for Oracle or SQL Server databases.|
mysql» update entity set «field»=«new value»; Example mysql» update entity set gs_swap_warn=50 mysql» update entity set gs_swap_crit=75
Refresh your GlobalScan view to see the new settings.
Changing Thresholds for a Single Element
To change the current thresholds for a single element within your up.time installation, complete the following steps:
The first command looks up the ID of the element that you want to update, and the second command applies the change. The command formats and an example are detailed below.
Replace the «display» text in the example below with the display name of the element for which you want to change the thresholds. Replace the «field» text in the example below with a value from the DataStore setting name column in the table above. Replace the «new value» text in the example below with your new threshold setting. The first command will return a value that you will need to use to replace the «id» text within the second command (decimal values can not be used for the new threshold).
mysql» select entity_id from entity where display_name='«display»'; mysql» update entity set «field»=«new value» where entity_id=«id»; Example: mysql» select entity_id from entity where display_name='my server'; ------ | 23 | ------ mysql» update entity set gs_swap_warn=50 where entity_id=23; mysql» update entity set gs_swap_crit=75 where entity_id=23;
Refresh your Global Scan view to see the new settings.
Changing the Default Values for New Elements
Configure different default GlobalScan threshold settings for all new elements that you add to up.time by completing the following steps:
The uptime.conf file is located in the base up.time installation folder.
globalscan.cpu.warn=70 globalscan.cpu.crit=90 globalscan.diskbusy.warn=70 globalscan.diskbusy.crit=90 globalscan.diskfull.warn=70 globalscan.diskfull.crit=90 globalscan.swap.warn=70 globalscan.swap.crit=90
On Solaris and Linux monitoring stations, restart the uptime_core service. On Windows monitoring stations, restart the up.time Data Collector service.
All elements that you add to up.time will use the GlobalScan thresholds specified in the uptime.conf file.