2.1.1 Flow of performance data collection

(1) Flow of data during performance data collection

The following figure shows the flow of data when performance data is collected.

Figure 2‒1: Flow of data when performance data is collected

• Flow of data in the collection process

  1. Connects to the monitored host and collects its performance data.

  2. Outputs the collected performance data to the temporary performance information file.

• Flow of data in the Remote Monitor Collector service

  1. Loads the temporary performance information file that was output by the collection process.

  2. Stores the loaded performance data as records in the Store database.

The Remote Monitor Collector service and the collection processes operate separately, each on its own schedule.

To Page Top

(2) Flow of processing during performance data collection

The following figure shows an example of the flow of processing when performance data is collected.

Figure 2‒2: Flow of processing when performance data is collected

#1

Because a temporary performance information file has not been created, data is not collected by collection processing at 00:05:00. The message KAVL17017-W is displayed.

#2

Consider the case when an alarm is bound between 00:15:00 and 00:20:00 during collection processing. This alarm might be evaluated at the 00:20:00 collection processing event (which is the first collection processing event after the alarm is bound). This depends on whether log information was collected in the record the alarm was bound to.

• The alarm is not evaluated if log information was collected.

• The alarm is evaluated if log information was not collected.

#3

As with collection processing at 00:15:00, the temporary performance information file output at 00:12:10 is loaded at the 00:20:00 collection processing.

If log information is being collected or if an alarm is to be evaluated, no performance data is collected. The message KAVL17016-W is displayed.

For collection processing based on real-time reports, the content of the temporary performance information file that was output at 00:12:10 is displayed, as was done at 00:15:00 of collection processing.

#4

Because the collection processing that started at 00:15:10 was not completed by 00:20:10, the collection processing that was scheduled to start at 00:20:10 is skipped.

Note

• When log information is stored in the Store database as performance data, the content being collected was actually created before the time of storage. The approximate time it takes from the collection of performance data to its storage in the Store database is at most the time specified in Interval during the instance environment setup (the default is approximately 300 seconds).

• The real-time report displays the content of the temporary performance information file that is in effect at the time the display operation is executed. If you refresh PFM - Web Console while a real-time report is being displayed, the content of the temporary performance information file that is in effect when you refreshed PFM - Web Console is displayed.

• Depending on the number of monitored hosts and the amount of data being collected, collection processing might lag.

• When you evaluate an alarm, the evaluation is performed on the performance data that was collected before the evaluation time. The approximate time it takes from the collection of performance data to the evaluation of an alarm is at most the time specified in Interval during the instance environment setup (the default is approximately 300 seconds).

  If you bind an alarm that uses a record that has not collected log information, the evaluation might be performed on the performance data that was collected farther back in the past depending on factors such as the timing of alarm binding and the lag in collection processing.

To Page Top