Job Management Partner 1/Performance Management User's Guide

5.10.2 Notes on displaying reports

The following gives cautionary notes on displaying reports:

About stacked area graph
If multiple series of records are stacked in a stacked area graph, only the records that have exactly the same time will be stacked.
Therefore, if you want to display stacked records from more than one agent in a historical (multiple agents) report, set the collection interval and offset value so that they match all of the agents.
If this condition is satisfied, a collection time difference might occur due to a delay caused by collection load and the stacked area graph might not display as expected. To avoid this, you can use an optional PFM - Web Console function to adjust the record collection time for the graph display.
For details, see the description of the <graph-time-correction> tag of the Windows initialization file (config.xml) in an appendix of the manual Job Management Partner 1/Performance Management Reference.

Maximum number of report windows displayed in the PFM - Web Console browser

The maximum number of report windows displayed in the PFM - Web Console browser is about four.

For report windows that display the PFM - Agent or PFM - RM information (report window displaying realtime reports), the maximum number of windows is roughly 10 for one Performance Management system. If 11 or more windows are displayed, you might fail to retrieve data.

Maximum number of data items displayed in a report
In realtime reports, data from 30 collection times can be displayed. When displaying data over 31 collection times, the data will be deleted in the order from oldest to newest data. If you want to change this maximum number, change the maxRealtimeCache in config.xml.
For historical reports, the maximum amount of displayed data of a data group is up to the maximum number of records or the maximum number set in the Windows initialization file (config.xml). If you want to change this maximum number, change the maxFetchCount (under the <vsa> tag).
Note that you cannot use the GUI to change a report that has too many records to display. Use the CSV output function of the jpcrpt command for such a report.

About data acquisition performance
If multiple realtime reports are displayed at the same time, data acquisition performance might be degraded.

Limitation of realtime report display
If multi-instance records are collected in PFM - Agent or PFM - RM, the maximum number of instances handled by a collection is 32,767. Therefore, when displaying the realtime report of multi-instance records in the browser, you can display no more than 32,767 instances. You cannot display 32,768 or more instances.

Displaying a report with a large number of records
If you use the GUI to display a report with a large number of records, the report might not be displayed due to insufficient memory. To avoid this, use the CSV output function of the jpcrpt command for such a report. For details on the jpcrpt command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

Too many graph legends to display
Although there are no restrictions on the number of fields in a report, the system might be unable to display the graph or legend in part or in its entirety if the report contains too many fields. We recommended that you limit the number of displayed fields to approximately 20.
If there are too many items in a graph legend, and some cannot be displayed, change the magnification of the graph to check whether all the legend information can be displayed. If some still cannot be displayed, add a field to the report table for each item in the legend that is not displayed.

[Contents][Back][Next]

[Trademarks]