Unit Utilization Level

Use unit utilization reports to identify under- and over-utilized systems in your Guardium environment.

Open the unit utilization reports by clicking Manage > Reports > Unit Utilization, and then selecting one of the reports.

The default unit utilization reports include the following:

Buff Usage Monitor
CPU Tracker
Enterprise Buffer Usage Monitor
Unit Utilization

Utilization Parameters

Most parameters are averaged for a specific unit over a specific time range. The number of restarts is a count of the sniffer restarts during a specific time range based on the different PIDs.

The parameters supported are:

Number of restarts
Sniffer memory
Percent MySQL memory
Free buffer space
Analyzer queue
Logger queue
Restriction: There is a limit of 500 SQLs in the logger queue. If more than 500 SQLs try to fill this queue at the same time, any additional SQLs beyond the queue limit will log RA=-1.
MySQL disk usage
System CPU load
System var disk usage
Number of requests
Number of full SQL
Number of exceptions
Number of policy violations
Quick search disk usage
Quick search number of documents
Flat log requests

Thresholds

For each parameter there are two thresholds defined that separate three utilization levels: Low, Medium, and High.

Utilization levels:

Low: value is less than Threshold1
Medium: value is greater than Threshold1, and less than Threshold2
High: value is greater than Threshold2

There is also an overall utilization level for each unit. For each period of time, this level is the highest level for all levels during that period.

Reporting

View the available unit utilization reports by clicking Manage > Reports > Unit Utilization.

The Unit Utilization Levels tracking option allows you to create custom queries and reports.

Using aliases is recommended when using unit utilization data in custom and predefined reports. Otherwise, utilization levels will display as numbers: 1, 2, 3, instead of Low, Medium, High.

The list of attributes includes:

Host name
Period start
Number of restarts
Number of restarts level
Sniffer memory
Sniffer memory Level
Percent MySQL memory
Percent MySQL memory level
Free buffer space
Free buffer space level
Analyzer queue
Analyzer queue level
Logger queue
Logger queue level
MySQL disk usage
MySQL disk usage level
System CPU load
System CPU load level
System var disk usage
System var disk usage level
Overall unit utilization level
Number of requests
Number of requests level
Number of full SQLs
Number of full SQLs level
Number of exceptions
Number of exceptions level
Number of policy violations
Number of policy violations level
Number of flat log requests
Number of flat log requests level

Note: Each parameter has a value and a level which is calculated based on the value and the thresholds.

Throughput information available in Unit Utilization

Throughput data is collected on each collector unit. The CM consolidates all throughput data and creates an enterprise custom table that is added to predefined utilization reports.

Throughput information collected:

Number of requests (for the period) (from construct instance)
Number of full SQLs (for the period) (from construct text)
Number of exceptions
Number of policy violations

By default, throughput information is collected every hour.

GuardAPI and CLI commands for Unit Utilization

Guard APIs:

listUtilizationThresholds

updateUtilizationThresholds

reset_unit_utilization

CLI commands:

store monitor gdm_statistics
show monitor gdm_statistics