Monitor Performance Using Experience View

apmdevops106
HID_Team_Center_Experience_View
Application Performance Management lets you understand the geography of your application environment, which is vital for effective monitoring and problem solving. Application Performance Management provides an overview of an application environment. The Experience View shows your monitored applications from the experience point of view.
The following roles use the Experience View:
  • Administrators see the health state of the environment.
  • Level One Analysts monitor problems and warnings in the environment with the Experience View.
  • Experienced analysts investigate and resolve problems with Analysis Notebook, Dashboard, and Map.
Understand the Frontend as an Experience
The Experience is the leftmost component of the transaction, the first monitored component of the whole transaction. The experience node is the first monitored frontend component and contains an attribute that is called Experience. The experience node is the beginning of the transaction path. An experience can be, for example, a servlet or a generic frontend. The experience node replaces the automatic entry point solution that had limitations, such as application-based granularity and application entry points data from mixed environments (for example, pre-production and production). The experience node resolves these limitations.
Experience View
Experience View lets you:
  • Filter out the nonproblematic parts of the environment to focus on the issues.
  • Drill down to lower levels of the Experience View to see sections of the environment in greater detail. Experience Cards show the status of all components for which you are responsible and highlight the experiences under load. Assisted Triage identifies the most likely problem areas and shows results in the Assisted Triage panel.
Transaction Types in the Experience View:
  • Healthy transactions -
    Responses per Interval
    metric values when the corresponding experience node has no alert in caution or danger state
  • Stall transactions -
    Stalls
    metric values of the experience node
  • Error transactions -
    Errors per interval
    metric values of the experience node
  • Slow transactions -
    Responses per Interval
    metric value when the corresponding experience node has an alert in caution or danger state on Average Response Time metric, or on a differential analysis metric
  • Alerted transactions -
    Responses per Interval
    metric value when the corresponding experience node has no alert in caution or danger state on a metric other than Slow transactions
Use the following graphic and corresponding legend to understand the various features in the Experience View.
ExperienceView10.7.png
The following legend identifies each map item by number and provides more information:
Number
Name
More Information
1
Return to the top-level view
2
Breadcrumb navigation
3
Time range
In Live Mode, select time increments up to 24 hours to view events over that period.
Note:
The selected time range saves when you exit Experience View. This time range reappears when you open Experience View.
4
Timeline Mode (Historical or Live)
The Timeline lets you move from the Live mode to Historical mode to see which status events occurred historically. You can select a Custom range up to 31 days to view Experience and Experience Card events for those ranges historically. The Custom range up to 31 days is only available in Experience View.
5
Expand or collapse the timeline
6
Go to Map
7
Online help link
8
Health Score
The Health Score shows the overall health score of the environment. The number shows a percentage of healthy transactions out of the total number of transactions. The score shows the volume of healthy and poor transactions. Poor transaction volume is a sum of all non-healthy transactions (slow, error, alerted, stalled).
9
Poor transactions
Poor transactions are the sum of slow and failed transactions:
  • Slow transactions are transactions that breached the Average Response Time alert threshold.
  • Failed transactions are transactions that triggered an alert or returned an exception. Failed transactions are a sum of Errors Per Interval (for the selected time range, for example, the last 24 hours) and Responses Per Interval at the time the experience has a CAUTION or DANGER state alert.
10
Total number of transactions
11
Return to the previous level
12
Perspective
A perspective logically groups components, and is based on their shared attributes.
13
Sort by
Name, My Order, Transactions Volume, Transactions Health, Experience Status, Error Count, Slow Count
14
Aggregated response time histogram
The histogram shows the average response time per seconds for healthy and poor transactions.
  • 1s
    Number of healthy transactions that are completed in less than 1 second.
  • 2s
    Number of healthy transactions that are completed from 1 through 2 seconds.
  • 2s+
    Number of healthy transactions that are completed in more than 2 seconds.
  • Slow
    Number of stalled and slow transactions. Transactions that breached the Average Response Time alert threshold.
  • Error
    Errors per interval metric values for the experience node.
Red indicates the number of alerted transactions that are completed.
15
Experience Card
Experience Cards show summary information and identify the problem and the problem origin. Cards are defined based on a universe. The maximum number is one universe within a card.
16
Open the Analysis Notebook
The Analysis Notebook displays the business transactions for a specific Experience Card. The business transaction count is visible next to the Analysis Notebook icon.
Note:
By default, you cannot open the Analysis Notebook if the Experience Card contains more than 20 business transactions.
17
Toggle graphs (Aggregated response time, Average response time, Transaction volume)
18
Culprit
Problems and anomalies are grouped by a possible culprit, which is the component that is suspected of creating the problem. The culprit application name is the name of the application on which the possible culprit appears.
19
Expand an Experience Card
Click the active area to expand the Experience Card and see more information.
20
Alert status
Alert status reflects the status of the monitored software component, business transaction, and their aggregated groups.
  • Green indicates normal - Values do not exceed the caution threshold.
  • Yellow indicates Caution - Values exceed the caution threshold.
  • Red indicates Danger - Values exceed the danger threshold.
21
Time series data (average response time graph, Transaction volume histogram)
Time series data provide the overview of metrics or a particular problematic time range. You are not limited to only events guidance. Hover over a peak in the metric behavior in the graph to select and zoom into a problematic time range.The responses per interval and errors per interval metrics are collected every 15 seconds.
Average response time graph
  • Blue line indicates the actual average response time.
  • Dotted line indicates a prediction of the average response time.
  • Shaded areas indicate a deviation. If the prediction value is outside the deviation range, something unusual is happening.
Note:
The different shades of blue indicate how normal the response time is based on historical data. The closer the response time is to predicted, the darker the blue color. Response times that are significantly outside of normal will not be within any blue area.
Transaction volume histogram
  • Divides the time range into 12 sections and compares the transaction volume within your selected time range.
22
Assisted Triage panel with Problems and Anomalies
A problem indicates a situation where one or more components in related transactions triggered alerts. Events like stalls, errors, and other evidences negatively impacted the transactions.
An anomaly indicates a situation where one or more components in related transactions has triggered alerts. Events like stalls and errors were noticed but did not impact transaction performance.
23
Collapse or expand the Assisted Triage panel
24
Completed error transactions
A red section in the histogram indicates the number of completed transactions with at least 1 alert on the experience node.
Monitor Performance Using the Experience View
The Experience View lets you monitor the performance of your environment from the highest level of your universe. You can drill down to specific transactions for fault finding.
Follow these steps:
  1. Click an
    Experience Card
    .
    The aggregated data for groups of related business transactions that are available in your universe appear. You can add cards, configure, and reorder the cards.
  2. Click the
    chart
    to cycle through the metrics charts.
  3. View the
    Health Score
    .
    The Health Score shows the overall health score of the environment. The number shows a percentage of healthy transactions out of the total number of transactions. For example, the health score of the environment that you monitor is 85. This score means that 85 percent of the transactions that you monitor are healthy. The remaining 15 percent are poor transactions. Poor transactions are the sum of slow and failed transactions.
  4. Expand a
    card
    .
    More details appear in the Assisted Triage panel. The Assisted Triage panel is a pull-out from the right and shows where problems and anomalies are occurring. The Assisted Triage engine identifies common components of a problem so that you are not flooded with issues. The Assisted Triage panel is visible in Experience View except for the top-level page.
  5. Expand the
    story
    .
    More details appear. The panel also shows suspect nodes, highlighted by the Assisted Triage engine as other possible contributors to the situation.
  6. Expand
    Problems and Anomalies
    .
    More details appear.
  7. Click the
    headline
    of the chart and drill down to the next level of grouping.
  8. Click the
    notebook
    icon.
    The Analysis Notebook for the group of components opens.
    By default, you cannot open the Analysis Notebook if the Experience Card contains more than 20 business transactions. For more information about Experience Cards, see TEC1315656.
Navigate Team Center
See how CA APM Team Center user interface evolved including a brief history of Team Center from version 10.0 to 10.5.1. This video focuses on the views and menu options.

Experience View Videos
The Experience View videos show the features of Experience View and Assisted Triage.
Introduction to Experience View
Understand how the Experience View helps you monitor components while promptly detecting and prioritizing problems that occur.

Building a Triage Using Experience View
Understand how the Assisted Triage Panel reports problems and anomalies about events in your system.

Example: Monitor and Isolate Issues Using the Experience View
Experience View lets you see the status of all components in the area of the environment that is your responsibility. You can see experiences under load and can drill down to identify critical components. Assisted Triage assists you to identify the most likely problem areas.
This example demonstrates a workflow for an analyst. As an analyst, you are aware of an issue in the environment. Identify the root cause of the problem and direct resources to fix the problems. The objective of diagnosing issues is to identify Patient Zero. Patient Zero is the component in the application which first encounters problems and affects other components and the customer experience.
The following diagram shows the workflow for monitoring an environment and isolating issues:
Homepage_workflow
Homepage_workflow
  1. Monitor the components in your environment.
  2. Click an
    Experience Card
    to drill down to see more detailed information in the lower levels of the Experience View.
    Application Performance Management detects the components that are experiencing problems and detects transactions that are running slowly or failing. The combination of slow and failed transactions is displayed as the total number of poor customer experiences. Experiences are prioritized based on the volume of transactions and the volume of poor customer experiences.
  3. Prioritize which issue is the most urgent based on volume. Look at the experiences suffering the greatest health issues. Correlate the experiences to the problems identified in the Assisted Triage panel. Prioritize which problems to solve based on business value.
    The Assisted Triage engine collects the information and displays the issues in the Assisted Triage panel. The Assisted Triage engine identifies transactions that share components that are performing poorly. Related components under load are identified together as a problem in the Assisted Triage panel.
  4. Consult the issue with more experienced analysts or a responsible person. Use the information in the panel to identify owners of components with issues. Share the URL with the person so that they can see the same view.
  5. Investigate the problem further in Analysis Notebook, Map, and Dashboard.