Performance Reporting Manager Software Bugs

One Hour Data Is Not Plotted in the Graph for Custom Time Selection (6619000)

The Performance Reporting Manager graphs can be generated for a user specified time range. In the Sun MC 4.0 release Performance Reporting Manager graphs, if the lower bound of the range and the time at which the data was generated are the same, the point is not displayed.

Workaround: Include an additional interval of half an hour or one hour at the lower bound.

For example, if there is hourly data for a certain property starting at 5.30, 6.30 and so on till 11.30, and if the graph is requested for the range between 6.30 and 10.30, the graph does not include the data point at 6.30. However, if the range is between 6.00 and 10.00, all the points are correctly plotted.

perftool Process Does Not Run When Performance Reporting Manager Is Incrementally Installed (6615241)

Incremental Performance Reporting Manager installation in a whole root zone does not configure the Performance Reporting Manager agent module.

Workaround: Modify the /var/opt/SUNWsymon/cfg/zone-modules-d.dat file.

Seven Days Performance Reporting Manager Reports Generation Takes a Lot of Time for 10 Data Properties (6611541)

When the number of agents being monitored and size of performance data is high, say over 100, generation of reports for the data of the last seven days takes very long. Seven days is the time limit from the current date till which the historical data at the smallest detail level is retained in the database. The smallest detail level is hourly. So, this report requires the database to retrieve the largest amount of data. The data size increases when the number of data properties requested for are more. Eight days also puts the same amount of stress on the database, since it retrieves data for seven days.

Beyond eight days, the historical data is retained at daily, weekly, and monthly intervals. Hence report generation for time ranges of over eight days is faster.

Workaround: When the number of agents is high, reduce the time limit for hourly data from seven days to five days .

Problem With Java Service Causes Performance Reporting Manager to Fail to Collect Agent Data (4855306)

If 15 or more Performance Reporting Manager report requests are scheduled to run simultaneously, you might encounter one or more of the following problems after the software has been running for a period of time:

• Data is not collected from agent machines

• Some report requests remain in a run state indefinitely

• Report requests cannot be scheduled as desired

• Grouping task requests cannot be scheduled as desired

• The Report Manager GUI cannot be launched

• The Manage Jobs GUI cannot be launched

For some of the previously mentioned problems, the console might display the following error message when you launch the Manage Jobs GUI:

Task Service is not available

Similarly, for some of these problems, the console might display the following error message when you launch the Report Manager GUI:

Report Service is not available

Workaround: When you encounter this problem, stop and restart your server components. Type the following commands:

# es-stop -A

# es-start -A

To avoid this problem, do not schedule more than 15 report requests to run simultaneously. Space the run time of scheduled requests over a period of time. For example, if you have 20 requests required to run every hour, split the requests into two separate batches, each containing 10 requests. Schedule the batches to run at 15–minute intervals. Do not schedule the batches to run simultaneously.

Alarms Reports Not Filtered Correctly When All Hosts Option Is Selected (4788475)

Alarms logged against agent machines are not filtered correctly in Alarms Reports when the All Hosts option is selected and a filter is specified.

When the All Hosts option is selected along with a filter, the specified filter criteria are applied to all the alarms that are logged for all the hosts. The filtered alarms are returned in the report output. Additionally, the report includes any Agent Not Responding alarms and Host Not Responding alarms from all monitored hosts. The specified filter criteria are not applied to such alarms.

Workaround: This problem can be avoided by explicitly specifying host names for Alarms reports. Choose from the following workarounds:

• When generating an Alarms report for a single host, either select the host name by providing the hostname:port, or select the host name from the Sun Management Center topology view.

• When generating an Alarms report for multiple hosts, either provide the different host names as hostname:port in a comma–separated list, or select the multiple host names from the Sun Management Center topology view.