Configuring a central manager for the deployment health views

To use the deployment health views, enable the collection of unit utilization data, configure correlation alerts, and configure data import and export for your environment.

About this task

From a central manager, the deployment health views display data from across a Guardium® environment. The ability to display data about an entire deployment requires the collection of unit utilization data, the configuration of correlation alerts, and that data import, export, and S-TAP® verification is correctly configured. For a summary of data that is displayed on the deployment health views, see Deployment health views.

It is likely that your deployment is already configured to support the deployment health views. Verify the configuration steps that are described in this procedure if you notice any of the following issues on any of the deployment health views:
  • CM buffer usage report not scheduled
  • Unit utilization report not scheduled
  • Export not scheduled
  • Import not scheduled
  • No issues found
  • Status unavailable

The S-TAP details include the inspection engines and their database versions if the auto-discovery feature is enabled. On Unix-Linux databases, auto-discovery is enabled by default and runs once daily. For more details, see Linux-Unix: Discover database instances. On Windows databases, auto-discovery is not enabled by default because it would overwrite user modifications to the inspection engine configurations. For more details, see Windows: Discover database instances

Procedure

  1. Configure the collection and processing of unit utilization data from the central manager.
    For more information, see Configuring unit utilization data processing.
  2. Enable correlation alerts for inclusion on the deployment health dashboard.
    1. Open Protect > Database Intrusion Protection > Alert Builder.
    2. Select an existing alert and click the modify icon, or create a new alert by clicking the new icon.
    3. Provide a Category for the alert.
      Alerts without a specified category are displayed as Uncategorized.
    4. Select the View in deployment health dashboard checkbox to include the alert on the dashboard.
      Attention: Alerts must have the Severity set to LOW, MED, or HIGH to be included on the deployment health dashboard.
      For more information about defining alerts, see Building alerts.
  3. Configure data import and export from the central manager.
    For more information, see, Data aggregation.
    Tip: Use the distribute configuration profiles tool to simplify the process of configuring data import and export for a Guardium deployment. For more information, see Working with configuration profiles.
  4. Configure S-TAP verification for all supported S-TAPs.
    For more information, see Windows Inspection engine verification and Linux-UNIX Inspection engine verification.

Results

After you complete the configuration procedures and allow the data to update, the deployment health topology and deployment health table views predominately show no health issues status except for systems with preexisting health issues. The deployment health dashboard includes any preexisting unit utilization issues and begins showing new correlation alert conditions.

After altering the unit utilization or data import and export schedules, wait up to 1 hour to allow the deployment health views to update with new information. The availability of new correlation alert data depends on the notification frequency that is specified for an alert.