NetOps Portal Dashboards timeouts

Products

• Network Observability
• CA Performance Management

Issue/Introduction

How to increase the timeout for report based queries in NetOps Portal.

Common Reporting Best Practices

What are some best practices for minimizing dashboard/report runtimes and database server load?

We're seeing NetOps Portal Dashboard reports report query time out errors. Sometimes the reports finish within the timeout period but performance slow and reports take too long to run. How can we improve the performance?

Environment

Network Observability DX NetOps Portal web server

Resolution

Best Practices

• Choose the shortest timeframe that satisfies your requirements. For example 'Last Hour' or a specific hour in the past would be faster than the Last 7 Days and narrowing focus from there.
• Select a Group with the smallest membership that satisfies your requirements. A focused report for a smaller subset of items will be faster to run and visualize the required data.
• When building custom Dashboards consider the number of queries issued by each dashboard View or graph/chart.
  • For example, Top N multi-trend style reports typically issue 1 query to determine the Top N, then, separate queries for each of the N items returned.
  • Given that the default for N is 10, a Top N style report leads to 11 queries. The more items the more queries the more load on the system.
• Ensure the Portal Memory Configuration is properly allocated.
  • Common indication of low or misconfigured memory allocation are frequent "Pinging the JVM" messages written to the PC wrapper.log file.
    • Default path is /opt/CA/PerformancCenter/PC/logs/wrapper.log
    • Current file is named wrapper.log.
    • The wrapper log is rotated/backed up daily.
    • Date is appended to name of old files.
  • To little, and sometimes to much, memory allocated to Portal services can cause performance issues when running reports.
  • See the Modify Maximum Memory Usage for NetOps Portal documentation topic for more details.
  • If slowness is rooted in DA responses to Portal report data requests, the DA may need memory allocation adjustments.
    • See the Modify Maximum Memory Usage for the Data Aggregator and Data Collector documentation topic for more details.
• If the systems are not properly resourced we can determine the correct requirements using the DX NetOps Sizing tool.