CA APM

Investigate Problems Using the Analysis NotebookThe Analysis Notebook lets you investigate further into individual problems. Follow these steps:

  1. When you identify an experience with apparent problems, open the Analysis Notebook.The Analysis Notebook shows the transactions that are affected in map format.
  2. Use the map Timeline to view events and alerts.
  3. Group the map with a predefined perspective or create your own perspective.
  4. Find components that are flagged as problems or anomalies.- A red circle indicates that the component is an actor in at least one problem or anomaly.- A concentric red circle indicates that the component is a culprit in at least one problem or anomaly
  5. Mouseover a component and click the icon.The Component Chart shows a maximum of 20 nodes. Use Component Charts to compare more live or historical metrics between arbitrary nodes. The Component Chart contains more metric information that is available for every component in the map. 
    • Aggregated Response Time Histogram
    • Average Sparkline
    • Transaction Volume Chart
  6. Click a component in the Relationship Flow.
    • The Metric Tree tab shows a contextual subset of metrics for the selected component.
    • The Performance Time Comparison tab displays a metric sparkline comparator. The right-hand column displays metrics from the current time. The leftmost column displays metrics for the same time from an earlier period. You can define the comparison time from the drop-down lists.Metric data appears in the metric viewer side by side with comparative metrics for an earlier period.
  7. Select the time period for the metric comparison using the drop-down list.The Assisted Triage engine analyzes the agent data from the monitored environment. The engine identifies connections and patterns between individual alerts that indicate a developing issue. The Assisted Triage Panel shows the detected problems and anomalies. Problems and anomalies consist of situations. Situations are grouped by culprit application name and sorted chronologically and by size;An anomaly indicates a situation where one or more components in related transactions has triggered caution alerts.A problem indicates a situation where one or more components in related transactions triggered warning alerts.
  8. Click a problem or an anomaly.Details about the problem or anomaly appear. The affected component is highlighted in the map.

Investigate Poor Transaction Performance – CA APM

Metric data, like the average response time of an important component, can inform you about the experience of customers using that component. However, this data does not help you understand cases where performance is unusually slow. When transactions are slow, a transaction trace can be something like an x-ray: showing details that are not visible from the surface, and letting you see where the transaction spent its time in a fine detail. Application Performance Management (originally Wily Introscope) pioneered the Transaction Trace approach to gaining deep insight into individual transactions. Transaction Trace monitors the activity of individual transactions as they flow through agent-monitored applications. While metric data tells you when there is a bottleneck in traffic, transaction traces can you tell you about the experience of a single car: where it was delayed, for how long, and even why. Transaction traces are stored, so you can view their details hours or days after the transactions first occurred.Find Traces of Slow or Failing TransactionsExperience View helps analysts find useful transaction traces to investigate. In the Business Transactions tab, analysts can then view transaction trace summaries and details. This information helps you understand transaction performance and solve poor performance by identifying when, where, and why performance degrades.Follow these steps:

  1. In the left pane, click Experience View.The Experience View shows individual experience cards. Each card shows a summary. Red items indicate slow or failing transactions.Note: For more information about Experience View, see Monitor Performance Using Experience View. You can also start your investigation from the Map. In the left pane, click Map, and skip the next step. For more information about the Map, see View Component Relationships in the Map.
  2. Browse the cards and click the Notebook icon on a card of interest.The Analysis Notebook shows details about the experience. The Relationship Flow shows the transaction paths of the selected experiences. This map gives context for the event that occurred.
  3. Analyze the map and identify a node (component) that is flagged as a problem or anomaly.- A red circle indicates that the component is an actor in at least one problem or anomaly.- A concentric red circle indicates that the component is a culprit in at least one problem or anomaly.This component might be the source of performance degradation in your application environment.
  4. Click either individual nodes or groups of nodes for a maximum of 1,000 nodes. Select the Application Layer or the APM Infrastructure Layer in the map to see all the traces that are collected by host, agent, or application.A component chart appears and shows healthy and poor transactions.Click here for component chart help…The component is highlighted in the AFFECTED APPLICATION COMPONENTS pane.
  5. Click the Business Transactions tab.A summary list shows traces that correspond to the component for the range that is selected in the timeline. Traces for inferred components, such as for backends, web services, or sockets are listed although these transactions are not monitored by agents. The traces show the duration times and are color-coded. Each color indicates a characteristic that is associated with a transaction, for example, red indicates an error. You can identify problematic methods by noticing the duration of the trace. Unexpectedly long traces are likely causes of slow transactions.
  6. Note: The list refreshes automatically when you use Live mode. The list shows the following trace information for a maximum of 2,000 traces.
    1. Url–The URL that was invoked to initiate this transaction, or the path to the component that initiated the transaction
    2. Name–The name of the high-level component, for example: Default
    3. Timestamp–The start time, in the system clock of agent host computer, of the invocation of the selected component
    4. Duration–The execution time in milliseconds of the selected component
    5. Trace Type–The type of trace: Error, Stall, or Other
    6. User Id–The ID of the logged-in user that is running the transactionThis information helps you understand the sequence of calls within a time period and evaluate performance.
  7. Note: Not all the information is available about deep visibility components.
  8. Perform one or more actions:
  9. Examine individual components and trace data. You can look at call sequence and inside the code to determine the cause of a problem.

Pages: 1 2 3

Leave a Reply

Your email address will not be published. Required fields are marked *