Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Example of creating a dynamic threshold


One approach to defining dynamic thresholds is to create the DEFAULT threshold set for an element that you want to monitor and associate that threshold set with the predefined ANYTIME calendar period. The DEFAULT threshold set will be in effect anywhere that element is used in BMC AMI Ops product views or alarm definitions. However, the same threshold set will be in effect all the time without regard for changes in your business activity.

Best practice
BMC recommends that you associate the DEFAULT threshold set for each element with the ANYTIME calendar period. This combination of DEFAULT threshold set and ANYTIME calendar period ensures that some form of threshold monitoring is in effect 24 hours a day, 7 days a week.

To create the DEFAULT threshold set for use with ANYTIME

  1. Use the MAKETHResh command on a BMC AMI Ops product view for an element that you want to monitor.
  2. On the THRSET view, add or change threshold comparisons for the element in the DEFAULT threshold set.
  3. Use the ENAble command on THRSET to make the DEFAULT threshold set available for use.
  4. Hyperlink to the THRSEL view to associate the DEFAULT threshold set for the element with the predefined ANYTIME calendar period.
  5. Use the ENAble command on THRSEL to make the DEFAULT/ANYTIME selection pair available for use.When you finish, the thresholds defined in the DEFAULT threshold set for the element will be in effect all the time.

To add a calendar period and another threshold set

To have different thresholds in effect for an element at different times, you need to define one or more calendar periods that reflect your business activity and at least one additional threshold set (in addition to the DEFAULT threshold set).

  1. Use the CALDEFS view to create a calendar period definition that represents a period of business activity (such as PRIME).
  2. On the CALDEF view, specify one or more time spans for the calendar period to indicate when the calendar period should be active (such as 08:00--18:00, Monday through Friday).
  3. Use the ENAble command on CALDEF to make the calendar period available for use.
  4. Use the MAKETHR command to add another threshold set (such as PRIMESET) for an element that already has a DEFAULT threshold set.
  5. On the THRSET view, add or change threshold comparisons for the element in the new threshold set.
  6. Use the ENAble command on THRSET to make the new threshold set available for use.
  7. Hyperlink to the THRSEL view to associate the new threshold set for the element with the calendar period you defined (such as the PRIMESET threshold set with the PRIME calendar period).
  8. Use the ENAble command on THRSEL to make the new threshold selection available for use.When you finish, the thresholds defined in the PRIMESET threshold set will be in effect when the PRIME calendar period is active (08:00--18:00, Monday through Friday). The thresholds defined in the DEFAULT threshold set for the element will be in effect at all other times.

To define standard calendar periods for multiple threshold sets

As an alternative, you can start with standard calendar periods that reflect your business activity (such as AM and PM, or WEEKDAY and WEEKEND), and use those calendar periods for multiple threshold sets that cover multiple elements.

  1. Use the CALDEFS view to create standard calendar period definitions that represent your business activity (such as SHIFT1, SHIFT2, and SHIFT3).
  2. Use the CALDEF view to specify one or more time spans for each calendar period (such as 07:00-15:00, 15:00-22:00, and 22:00-07:00, every day of the week).
  3. Use the ENAble command on CALDEF to make the calendar periods available for use.
  4. Use the MAKETHR command to create threshold sets for the elements that you want to monitor (such as SHIFT1SET, SHIFT2SET, and SHIFT3SET for each element).

    Note

    Remember that the first threshold set you create for each element is called DEFAULT. You can create additional threshold sets for an element and call them anything you want.

  5. On the THRSET view for each threshold set, perform the following actions:

    • Add or change threshold comparisons for the element.
    • Use the ENAble command to make the threshold set available for use.
    • Hyperlink to the THRSEL view to associate the threshold set with the appropriate calendar period (such as SHIFT1SET with SHIFT1).
    • On the THRSEL view, use the ENAble command to make each threshold selection available for use.

    When you finish, multiple threshold sets called SHIFT1SET (each for a different element) will be in effect when the SHIFT1 calendar period is active (07:00-15:00). The same would be true for the SHIFT2SET and SHIFT3SET threshold sets. This approach provides a standard way to monitor multiple metrics during each shift.




 

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