Skip to main content

BMC Helix Alarm Policies

MetricsHub ships with the following alarm policies for BMC Helix:

Alarm PoliciesWhen to useAlarms triggered when
SystemWhen monitoring of operating systems and OS-level resources is configured (filesystem, memory, network, paging activity)
  • Filesystem utilization is too high or free space is critically low
  • Available memory is critically low
  • Network errors or packet drops are detected
  • Paging activity is abnormally high
HardwareWhen monitoring of physical or virtual hardware components is configured (CPU, memory, disks, fans, power supplies, network interfaces, etc.)
  • A hardware component is missing (not present)
  • A hardware component is degraded
  • A hardware component has failed
  • A hardware component is predicted to fail
  • Hardware performance metrics cross warning or critical thresholds (e.g. battery level, fan speed, GPU utilization)
  • Hardware errors are detected (e.g. disk or network errors)
  • Connectivity or operational state is abnormal (e.g. network down, blade powered off)
StorageWhen monitoring of storage systems is configured (controllers, pools, volumes)
  • Storage controllers experience high utilization
  • A storage pool is degraded or failed
  • A storage volume is degraded or failed