CA APM

Monitor the Overall Health of the Environment with Dashboard – CA APM

Application Performance Management provides an overview of an application environment. The Dashboard shows the overall health of the environment. A tile represents a group of all components that share an attribute name and value. The tiles show the most significant differential analysis and alerts status of any of the components in the group.OverviewThe Dashboard tiles are organized in columns. Each column represents an attribute from the selected perspective. The attribute name is in the column header. Each tile within a column shows status of all components that have a specific attribute value.

The following legend identifies each map item by number and provides more information:

View Layers in the Dashboard Layers let you apply the standard Application Performance Management views to the dashboard, for example, Agent View and Experience View. Switch between the following layers in the dashboard:

• Application Layer shows components in the map. Components correspond to the Experience cards in Experience View.
• APM Infrastructure Layer Shows Enterprise Managers and Agents in the dashboard. This layer corresponds to the Agents View.
• Infrastructure Layer Shows the network infrastructure of your environment including Docker Monitors.

Assisted Triage and Analysts

Assisted Triage is an engine and story generator. Assisted Triage identifies the most meaningful events that occurred in your busy systems and provides contextualized information (stories) about these events. These stories appear as problems and anomalies with headlines. The reliable and intelligent nature of the stories that Assisted Triage generates keeps you fully apprised of the state of your monitoring domain.

Assisted Triage creates problems and anomalies about events in your system. Assisted Triage reacts to the following types of events:

• Stalls
• Errors
• Alerts
• Unstable response times

Problems and anomalies explain aspects of one or more events. For example, the aspects include:

• WHAT summarizes the event including any suspected causes (the WHY). This information appears as a headline for a problem or anomaly in the Experience View and Analysis Notebook.
• WHERE locates an event occurrence, typically information like the host and agent name. WHERE can have more details when available.
• WHO identifies the transactions that are affected or might be impacted. This aspect also determines how many transactions are affected.
• WHEN records an event occurrence; typically the start and end of a stall event, an error event, or an instability.
• WHY explains an event occurrence. For example, the following statement explains a high-call ratio problem:Potential high call ratio from ViewOrders|service to 138.0.0.1_7080|getService 2 in the order of 214980

The following diagram and corresponding steps describe how Assisted Triage works:

1. Events in your APM system occur as variance intensity, errors, stalls, APM alerts, and so on. An event contains a possible suspect for causing the problem.
2. An event generator gathers event data from different sources and sends the data to the event processor.
3. The event contextualizer receives the events from generators across a cluster, processes the events, and gathers any related events into a context. The context information includes the potential impact of the leftmost component, and all the transactions that flow through the component.The contextualizer passes this context information to the editor.
4. The editor tracks different contexts and assigns one reporter per specific event context for further analysis.
5. Reporters know the different types of analysts that are available in the system, and run the context through each analyst. Analysts analyze the context for event types, patterns, and potential impact, and then each analyst creates a statement. Analysts work together to record evidence or create stories from the statements, and then store the data in the APM database. Stories are purged from the database when they are older than 62 days.
6. The stories appear as problems or anomalies on the Experience View and Analysis Notebook.

Note: The Enterprise Manager generates and collects metrics about the Assisted Triage components. These supportability metrics are useful in assessing the Enterprise Manager health.AnalystsAnalysts are like medical specialists who know how to diagnose specific classes of illnesses. Assisted Triage uses the following main types of analysts. Each type of analyst includes other specific analysts. Event analysts look for certain event types and create event statements that serve as evidence. Examples of event analysts include:

• A Differential Analysis analyst checks for variance intensity
• An error analyst checks for error events in contexts
• A resource event analyst monitors alert events on system resources

Pattern analysts look for certain patterns in the context and create pattern statements. These statements are one part of a story summary. Examples of pattern analysts include:

• A default analyst determines the deepest component in a context (per the relationship map). The default analyst is also referred to as the Zone Identifier.
• A High Call Ratio analyst looks for the deepest component in the given context (per the relationship map). This analyst sees if the component calls any backend type nodes an unusual number of times.

Investigate Problems Using the Analysis Notebook

Application Performance Management lets analysts perform specific tasks for their role. Use the Analysis Notebook to investigate issues.

Use the following graphic and corresponding legend to understand the various features in the Analysis Notebook.

The following legend identifies each map item by number and provides more information:

Pages: 1 2 3