Previous Topic: OperationsNext Topic: Example 2: Performance Problem with a Server


Example 1: Performance Problems with an Application

A user from corporate headquarters reports they are experiencing a problem with an application.

Approach

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

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

    The Performance by Application page opens.

  3. Determine if the reported application has bubbled up in the list to the top. Typically it is among the top ten. If the application does not appear in the top ten, change the Size setting to a larger value until the application appears in the list. If the application is not in the list, it might not be monitored by CA Application Delivery Analysis.

    Worst-performing applictions bubble-up to the top of the list.

  4. Click the performance bar to the right of the application name to display a detail page. From the detail page, you can narrow the scope of data by clicking a network or server metric.
  5. If the network 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 application to identify and note any systematic patterns of unavailability or performance degradation.

    View historical data for a network, server, or application to analyze performance behavior over time.

  8. In the Show Me menu, you can also click Performance and then click Explore to begin troubleshooting. You can also do more exhaustive troubleshooting by clicking Links: Engineering at the top of the page to display the Response Time Component Delays page. Notice the selected application name and server or network name in the query selection box at the top of the page.
  9. Review the Response Time Composition: Average view, and pinpoint the time that the reported issue occurred. Identify which component is the most significant contributor at that point in time.