![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Performance Management User's Guide
- Organization of this subsection
- (1) Time for evaluating the alarm
- (2) Saving of records to be evaluated in the alarm
- (3) Limitation on the number of alarms
- (4) When you set an alarm to monitor whether a value exists
- (5) How the number of alarm occurrences affects the PFM - Agent or PFM - RM connection
- (6) How the number of alarm occurrences affects the system resources
(1) Time for evaluating the alarm
If monitoring conditions of multiple records are set for an alarm and the monitoring intervals and offsets of the records are different, the alarm is only evaluated when their collection schedules match. You must review the collection interval setting if necessary.
(2) Saving of records to be evaluated in the alarm
You do not have to save the records that you selected for the alarm conditions in the Store database.
(3) Limitation on the number of alarms
You can register up to 50 alarms in one alarm table. In addition, you can bind up to 50 alarm tables to one agent.
Binding a large number of alarms to PFM - Agent or PFM - RM in the Performance Management system, might delay the processing of PFM - Manager, PFM - Agent, or PFM - RM.
We recommend that you limit the number of bound alarms to the following:
- 250 alarms per agent.
- 10,000 alarms across the entire Performance Management system.
(4) When you set an alarm to monitor whether a value exists
If you have selected Monitor whether the value exists, the value specified in the conditional expression does not exist when the alarm is reported. In such a case, note that any variables specified in message text or in Mail Subject are replaced by an empty string.
(5) How the number of alarm occurrences affects the PFM - Agent or PFM - RM connection
In Performance Management, the PFM - Manager receives the alarms issued by PFM - Agent or PFM - RM, and handles them sequentially, for example, by storing them in the Store database (Master Store). When alarms occur more frequently or are issued by many PFM - Agents or PFM - RMs at the same time, the processing of PFM - Manager might be delayed. In such a case, unhandled alarms are accumulated in the memory of the PFM - Manager host, which might cause the memory usage to increase or the system performance to degrade.
We therefore recommend that you consider how frequently an alarm will occur when you define it, to avoid exceeding the maximum number of alarm occurrences that PFM - Manager can handle in a particular unit of time. We also recommend that you determine the number of PFM - Agent or PFM RM instances to be connected to PFM - Manager, beforehand. For details on the relationship between the alarm damping and the number of PFM - Agent or PFM - RM instances to be connected to PFM - Manager, see the sections that describe the system configuration in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.
(6) How the number of alarm occurrences affects the system resources
If a large number of alarms for which an action is specified are issued at the same time, when the actions are executed, the system might become unstable due to a large consumption of system resources.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.