Transición a la democracia

front-end tier.

Application with Two Front-end Tiers

For example, there may be two front-end tiers that match your application. The first tier is based on transactions originating from Enterprise Synthetic agents, referred to as Synthetic. The second tier is based on sequence transactions, referred to as RUM sequence transactions. For more information, see Configuring Tiers on CAS in the Data Center Real User Monitoring Administration Guide and Multi-Tier Reporting [p. 98].

If traffic is detected on both front-end tiers for your application in the last monitoring interval: • In the Application column, you will see two rows with your application name. This is

because there is data for both front-end tiers for your application.

• In the Tier column, you will see both front-end tiers for your application: Synthetic and RUM sequence transactions next to your application name displayed in the Application column.

Figure 29. Application with Two Front-end Tiers

Applications Report

The Applications report presents all applications for which data was detected on front-end tiers. By default, the report shows data for the current day with a one-hour resolution. The Applications (High Resolution) report shows this data with finer granularity (a resolution of one period).

How to Access the Report

From the CAS top menu, choose Reports ➤ EUE Overview ➤ Applications. The report displays data if:

• You have configured at least one application on the CAS or your CAS receives information about applications from Enterprise Synthetic Agent Manager.

• The traffic is detected on a front-end tier and the tier matches your application definition.

NOTE

If the CAS is configured to receive data from Enterprise Synthetic Agent Manager, the Applications report will automatically show the applications originating from Enterprise Synthetic.

The high-resolution version of the report is accessed from the Application Performance Overview chart when you click a selected point on the chart. This report shows the same metrics as the Applications report, but presented values reflect measurements for the selected time range with a resolution of one period.

Report Contents and Usage

This report helps you identify applications with performance or availability problems. Data is presented both on a chart and in a table.

You should start analyzing data by looking at the Application Performance Overview chart, which shows the performance of the top five applications (according to the number of unique users) over the selected period. If you notice a significant drop in application performance at a particular hour, click that point on the chart to see more details.

Figure 30. Application Performance Overview Chart

The tabular report lists the defined applications. Each row represents one application and shows metric values corresponding to the front-end tier for the application. You can see that tier name in the Tier column. The most important statistics include Performance, Unique and affected users (performance), and Errors that occurred over the analyzed period of time.

In addition to numeric data, the tabular report includes status icons to indicate different levels of problem severity. If there were performance or availability problems with any of the listed applications, you will see a yellow, orange, or red status icon in the Performance, Unique and affected users, or Availability column. In this case, click the application name to display a layered view of the application and see whether the problem is the network or the data center. For more information, see Network Performance Calculations [p. 389].

The report has additional Tiers and Sites perspective tabs that enable fast switching to other global views of your monitored environment.

Drilldown Reports

You can access more detailed reports from the following columns: • Application

◦ Tiers report. Use this report to see the division of layers for a selected application and to locate and isolate the problem.

For more information, see Tiers Report [p. 111].

◦ Transactions for Application report. Use this report to identify transactions that cause application performance problems.

For more information, see Transactions for Application Report [p. 110].

◦ Sites report. Use this report to identify sites in which application performance problems occur and to see how the problems affect the users of a specific application.

For more information, see Sites Report [p. 123]. ◦ Metric Charts for Application Tiers report.

For more information, see Metric Charts for Application Tiers in the Central Analysis Server Online Help.

◦ Dynatrace Application Monitoring Client (only for the HTTP traffic that is monitored both by DC RUM and Dynatrace Application Monitoring).

◦ RUM Browser - User Actions report.

For more information, see RUM Browser - User Actions [p. 188]. • Unique and affected users (performance)

◦ All Users report (for data center tiers).

For more information, see All Users Report [p. 161]. ◦ All Users for Client Tiers report (for client tiers).

For more information, see All Users Report [p. 161].

◦ Application Performance Affected Users report (for data center tiers).

For more information, see Application Performance Affected Users Report [p. 162]. ◦ Application Performance Affected Users for Client Tiers report (for client tiers).

For more information, see Application Performance Affected Users Report [p. 162]. ◦ Network Performance Affected Users report (for data center tiers).

For more information, see Network Performance Affected Users Report [p. 162]. ◦ Availability Affected Users report (for data center tiers).

For more information, see Availability Affected Users Report [p. 163]. ◦ Availability Affected Users for Client Tiers report (for client tiers).

For more information, see Availability Affected Users Report [p. 163]. • Failures (total)

◦ Application responses report (for data center tiers).

For more information, see Application Responses Report [p. 160]. ◦ Synthetic Errors (Unavailable Transactions) for synthetic tiers.

For more information, see Synthetic - Unavailable Transaction Summary [p. 141]. ◦ Errors for Client Tiers report (for client tiers).

For more information, see Errors Report [p. 160].

◦ Dynatrace Application Monitoring Client (only for the HTTP traffic that is monitored both by DC RUM and Dynatrace Application Monitoring).