End-user experience monitoring platform alarms

BMC Real End User Monitoring components share a platform layer that provides common features, such as the alarm framework. The alarm framework simplifies Customer Support activity by passing low-level system information and by performing corrective actions for simple problems. The alarm framework is invoked every 60 seconds.

The following example shows an alarm received in email.

Date: 2013-02-06 19:06:02 -0800

Source: Company Analyzer

Severity: attention

Name: storage.performance.io \[raised\]

Description: Performance of drives sdb does not match data processing volume.

The following topics describe the characteristics of a platform alarm and how you view or receive the alarms.

For a detailed list, see the Platform alarm reference.

Alarm characteristics

You use the alarm command to display a list of active alarms for a component and to set platform alarm properties.

Alarm output mechanisms

When an alarm is raised by the system, it is sent to the internal syslog file. You can receive the alarms in a system log, by email alerts, or by SNMP trap alerts.

• System log - You can send a copy of the syslog entries to a remote syslog server. The syslog will contain a line entry from “alarmMonitor.”
• System alert email - You can use the same mechanism for emailing alerts to route platform alarms.
• System alert SNMP trap - You can use SNMP traps to send alarms to an SNMP manager.

Consult the following topics for information about how to configure these mechanisms to receive alarms:

• Remote logging
• syslogparams command
• Enabling email notification of system alerts with SMTP
• Enabling SNMP for BMC End User Experience Monitoring
• snmpconfig command
• Connecting the Aggregation Server to a mail server (SMTP) 
• Enabling email alerts or a remote syslog server for the Aggregation Server
• dnsparams command

^{Contributed by BaoPhac Do.}