OpsCenter reporting best practices

This section talks about a few best practices that you should follow while generating OpsCenter reports.

Scenario 1 - Pie chart reports may slow down the OpsCenter GUI service

Note:

Assumption - OpsCenter database cache size tuning is in place.

Solution: You need to tune the OpsCenter GUI service for reporting.

The recommended average report time frame is 15 days. If the timeframe is more than 15 days and if you want to generate a chart-based report, then increase the GUI (web server) service heap size to a value between 2 GB and 4 GB. If you observe performance issues even after increasing the heap size, increase the OpsCenter Server service and GUI service heap size beyond the recommended sizes.
See Adjusting the default heap size for the OpsCenter web server service.

Note:

Once you have changed the heap size, restart the OpsCenter services.

Scenario 2 - OpsCenter performance may be affected while generating scheduled or custom reports

Solution: You need to define good time frame for scheduled reports as well as custom reports

If the number of scheduled reports is more than 300, use the recommended average report time frame that is 15 days.
Make sure that multiple reports are not running in parallel. Schedule the reports at different times as much as possible.
Schedule graphical (chart-based) reports at different times than the tabular reports, because graphical reports require more amount of memory to generate the output.
Increase the OpsCenter Server service heap size. Set the heap size to a value between 4 GB and 8 GB.
See Adjusting the default heap size for the OpsCenter server service.

Note:

Once you have changed the heap size, restart the OpsCenter services.