Eventing › Monitoring Metrics with Event Rules › Create a Monitoring Profile and Add Event Rules

Create a Monitoring Profile and Add Event Rules

To set up the process of monitoring the performance of the virtual servers in your custom Virtual Servers device collection, you first create a monitoring profile and add event rules to that monitoring profile.

Event rules are not included in factory (out-of-the-box) monitoring profiles, and you cannot modify factory monitoring profiles to add event rules. You copy an existing monitoring profile to use as a basis for creating a similar profile with some changes. The changes that you will make to the custom monitoring profile will be to add event rules.

Working with the IT Architect and Operations Center Manager, you decide to create a monitoring profile and add the following event rules:

• Add a VMware memory utilization rule, as follows:
  • Violation occurs when memory utilization is above 80 percent for 300 seconds (5 minutes) within a 900-second (15-minute) window.
  • Clear the violation when the memory utilization is equal to or below 75 percent for 300 seconds within a 900-second window.
• Add a VMware CPU utilization rule, as follows:
  • Violation occurs when both of the following conditions are met:
    • Condition 1: CPU utilization is above 70 percent.
    • Condition 2: CPU utilization is above one standard deviation.
  • These conditions occur for 300 seconds within a 900-second window.

Follow these steps:

1. Select Admin, Data Source Settings, and click a Data Aggregator data source.
2. Click Monitoring Profiles from the Monitoring Configuration menu on the Data Aggregator administration page.

   A list of monitoring profiles is populated.

3. Select the Virtual Server monitoring profile and click Copy.

   The Create/Edit Monitoring Profile dialog opens.

4. Change the name of the monitoring profile to Custom Virtual Servers.
5. Click Save.

   The copied monitoring profile is added to the Monitoring Profiles list.

6. Select the Custom Virtual Servers monitoring profile.
7. Click the Event Rules tab.
8. Create the VMware memory utilization event rule as follows:
   1. Click New.
   2. Enter the following values for your new event rule:
      • Name: VirtualMemUsageTooHigh
      • Description (optional): VMware memory utilization
      • Metric Family: VMware Virtual Machine
      • Duration: 300

        Note: In this example, we assume that devices are polled at the default rate of 300 seconds. The Duration value is used for the violation threshold and the clear threshold.

      • Window: 900

        Note: The Window value is used for the violation threshold and the clear threshold.

      • Severity: Major
   3. In the 'A violation occurs when all of these conditions are met' section, select the following values:
      • Metric: VM Memory Utilization
      • Operator: Above
      • Value: 80
      • Condition Type: Fixed Value
   4. In the 'A violation is cleared when' section, select the following values:
      • Operator: Equal to or Below
      • Value: 75
   5. Click Save.
9. Click the Event Rules tab.
10. Create the VMware CPU utilization event rule with multiple conditions, as follows:
    1. Click New in the Event Rules group box.
    2. Enter the following values for your new event rule:
       • Name: VMwareCpuUtil
       • Description (optional): VMware CPU utilization
       • Metric Family: VMware Virtual Machine
       • Duration: 300
       • Window: 900
       • Severity: Major
    3. In the 'A violation occurs when all of these conditions are met' section, select the following values:
       • Metric: CPU Utilization
       • Operator: Above
       • Value: 70
       • Condition Type: Fixed Value
    4. Click Add Condition.
    5. In the 'A violation occurs when all of these conditions are met' section, select the following values:
       • Metric: CPU Utilization
       • Operator: Above
       • Value: 1
       • Condition Type: Standard Deviation

       Note: Multiple condition event rules are limited to metrics within a single metric family. In this example, we assume that the metric family is already available for use in Data Aggregator. For more information about creating a custom metric family, see the Data Aggregator Self-Certification Guide.

       When you define multiple conditions, the clear event is issued when any of the conditions are no longer true.

       Important! It can take up to 48 hours from when you start monitoring a metric family for Data Aggregator to calculate baselines for every hour. Baseline data is needed for standard deviation rules.

11. Click Save.

    Your event rules are saved. The event rules are filtered to metric families in the Custom Virtual Servers monitoring profile to help ensure all of the rules you define are evaluated.