Previous Topic: Example 2: Performance Problem with a ServerNext Topic: Investigations

Reporting › Troubleshooting › Operations › Example 3: Performance Problems with a Network

Example 3: Performance Problems with a Network

An end user from corporate headquarters reports they are experiencing a problem with a specific network.

Approach

Gather the problem information from the user and create a trouble ticket.

  1. Click the Operations page.
  2. Click Networks in the Show Me menu.

    The Performance by Network view opens.

  3. Determine if the reported network has bubbled up in the list to the Top N. If the network does not appear in the Top N, change the Size: setting to a larger value until the network appears in the list. If the network does not appear in the list, it might not be monitored by CA Application Delivery Analysis.

    An example of the Performance by Network view.

  4. Select the performance bar to the right of the network name to display the detail page. From the detail page, you can narrow the scope of data by clicking an application or server metric.
  5. If application or server is known, select the appropriate performance bar to further narrow the scope.
  6. In the Show Me menu, click History.
  7. Review the history of the network to identify and note any systematic patterns or trends.
  8. Select Links: Engineering at the top of the page to display the Response Time Component Delays page. You should notice the selected network name and/or server or application name in the query selection box at the top of the page.
  9. Review the first view, the Response Time Composition: Average view, and pinpoint the time on the view the issue is reported to have occurred. Identify which component is the most significant contributor at that point in time.