Skip to Content

Monitoring database status

Use the Database status page to monitor the state of the Aggregation Server for Extended Reporting performance cubes. The following figure illustrates the Database status page.

DatabaseStatus.png 

This tabular page is divided into columns for each of the aggregation subjects. By default, the tables display summary information. To view more detailed information, you can expand the tables. Columns are further subdivided to show information per performance cube.

Performance cube database space usage

Each performance cube aggregation subject has a storage limit. The Space used row shows the percentage of that limit used by each performance cube. The amount of space used by each performance cube should correspond to the relative importance of that performance cube for what you want to report on.

To manage the space used, disable (or modify) performance cubes whose growth is disproportionate to their importance.

The aggregation intervals for the aggregation subjects are defined as follows:

  • Application: 5-minute, hourly, daily
  • Infrastructure: 1-minute, hourly, daily
  • User: hourly, daily

For each aggregation interval, the table displays the actual retention period (maximum age of data) versus the reserved storage space (expressed as a maximum retention period) and the total number of records per performance cube.

Data that exceeds the maximum retention period is trimmed from the database to free up space for new data.

Dimension unique keys

The Unique keys row displays the number of unique keys per performance cube. Unique keys is a count of unique combinations of values per performance cube. The Unique values observed row displays a count of unique values per custom field/dimension. The sum of the unique values does not necessarily equal the number of unique keys per performance cube.

The greater the number of unique keys, the slower your Aggregation Server device performs. You also risk reaching the maximum capacity for data storage, and when this happens, the retention period is dynamically shortened.

Information
Example

If you are tracking users, there can be a unique key for each of them. But you might not need the ability to identify all users uniquely. It might be sufficient to track them by geographical location instead, or by browser type or operating system. And doing so would reduce the number of unique keys.

Following are the recommended maximum number of unique keys per performance cube per aggregation subject.

  • Application cubes: 10,000 unique keys per 5-minute period; 10,000 unique keys per hour; 100,000 unique keys in the history of the performance cube
  • Infrastructure cubes: 15,000 unique keys per minute, hour, and day; 100,000 in the history of the performance cube
  • User cubes: 500,000 unique keys in the history of the performance cube

To check the database status

  1. Log on to the Aggregation Server for Extended Reporting web interface.
  2. Click Database status on the Device status page.
  3. Expand the Unique keys section.
  4. After 15 minutes, confirm that unique keys are incrementing.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC TrueSight App Visibility Manager 2.7