6.9.3 Notes on evaluating alarms
This subsection provides cautionary notes on alarm evaluation.
- Organization of this subsection
(1) Limitation on the number of instances evaluated in an alarm
If multi-instance records are collected in PFM - Agent or PFM - RM, the maximum number of instances handled by a collection is 32,767. When alarms are bound to PFM - Agent or PFM - RM, up to 32,767 instances are evaluated. More than 32,767 instances cannot be evaluated.
(2) Interval for evaluating the alarm
An alarm is evaluated at fixed intervals. The interval is the record collection interval for each agent. For details on the collection interval of each record, see the appropriate chapters (the Collection Interval value of each record) that describe records of each PFM - Agent or PFM - RM manual.
To modify the record collection interval, perform the following procedure:
-
From the Web browser of the monitoring console, log on to PFM - Web Console.
-
In the navigation frame of the main window, select the Services tab.
-
Select the monitoring agent that the alarm is bound to.
-
In the method frame, select Properties.
-
Expand the Detail Records or Interval Records folder.
-
Change the value of the Collection Interval property.
-
The record (performance data) collection interval changes to the value you set.
(3) Character encoding during alarm evaluation
If you use Japanese or Chinese in an alarm definition, the instance of PFM - Agent or PFM - RM to which the alarm table is bound must use the same character set as PFM - Manager. If the agent or PFM - RM uses English or a different character set, the following can occur:
-
Characters appear garbled in the Event Monitor
-
Message displayed when an action is executed appear garbled
-
The status of an alarm remains normal in PFM - Web Console despite the alarm definition indicating an abnormal or warning status
-
An alarm does not enter normal status in PFM - Web Console despite the alarm definition indicating a return to normal from abnormal or warning status
The character set used by the Performance Management services is determined as follows:
-
When started by a command
The character set specified in the environment where the jpcspm start command is executed applies.
-
When started automatically at OS startup
The character encoding set when the OS starts applies.
In UNIX, if the character set applied at OS startup is not the character set you want to use with Performance Management, enter a character code setting in the service automatic start script (jpc_start).
(4) Evaluating alarms when PFM - Agent or PFM - RM is stopped
When PFM - Agent or PFM - RM is stopped, alarms are evaluated as follows.
-
If you stop the PFM - Agent or PFM - RM service while it is in abnormal or warning status, all of the alarms in the alarm tables bound to PFM - Agent or PFM - RM revert to normal status. When PFM - Agent or PFM - RM restarts, the evaluation process begins again from a normal status, not the status at the previous startup.
-
If you stop the PFM - Agent or PFM - RM instance to which an alarm table that contains an alarm for which damping is set is bound, the alarm damping measurement is reset.
When the PFM - Agent or PFM - RM restarts, the measurement also restarts.