The Oracle-defined dashboards for Application Performance Monitoring provide insights into the key elements of your application during a selected period of time.

The Oracle-defined dashboards are listed on the Dashboards page. Click the name of the dashboard to view the dashboard and specify the following details:

• Select the compartment in which your APM domain resides. Note that if a compartment is selected on the Dashboards page, then it's displayed by default.
• Select the APM domain that contains the systems being monitored by Application Performance Monitoring.
• Select the resource that you want to monitor. For example, in the App Server dashboard, select an application server in the App Server drop-down list.
• Select the time period for which you want data to be populated in the dashboard.

After you specify the details, the dashboards are populated with data and provide a quick insight into the health and performance of your application and enable you to identify the area that requires your attention.

Here's information on the Oracle-defined dashboards for Application Performance Monitoring:

• The WebLogic Domains dashboard provides an overview of the WebLogic metrics and enables you to monitor the performance of administration and managed servers in Oracle WebLogic Server. In this dashboard, select a WebLogic domain and a server that belongs to the domain and monitor the CPU load, free heap percentage, and other metrics. For more information, see Application Performance Monitoring Dashboard in Using Oracle WebLogic Server for OCI.
• The App Server dashboard is the Home page for your application servers and enables you to analyze the resources used by your application servers and understand resource constraints and requirements. For instance, you can monitor this dashboard to analyze the heap and CPU usage of your application server.
• The Monitors dashboard provides an overview of your synthetic monitor runs. This dashboard displays the total monitor runs, the monitor runs on critical vantage points, load time, and so on. This enables you to proactively find and fix issues before they impact the end user. The Monitors dashboard also displays the list of monitors in the APM domain, and you can click the name of the monitor and navigate to the monitor details page.
• The Real User Monitoring dashboard provides an insight into the performance of your web application and user experience. The Web Application drop-down list allows you to select a subset of data for which information is displayed in the widgets, such as, Apdex, Response Time, and Operating Systems. This enables you to measure the speed and performance of your web application and take corrective action to enhance user experience. The Real User Monitoring dashboard also displays the Real User Data Metrics widget, which allows you to select a metric in the Metric drop-down list and view high or low values by continent for the selected metric.
• The Home dashboard provides an overview of the availability and performance of the services being monitored by Application Performance Monitoring in an APM domain. The Home dashboard also acts as the Home page for Application Performance Monitoring and you can access this page from the Oracle Cloud Infrastructure console navigation menu.

  The Home page includes widgets that provide snapshots of the application servers, monitors, services, traces, and web applications in the APM domain and you can click the links available in these widgets to navigate to a specific dashboard or Trace Explorer. In addition, the Home page also displays the Alarms widgets, which enable you to monitor the firing alarms created for the metrics in the Application Performance Monitoring namespaces in the Oracle Cloud Infrastructure Monitoring service. You can click the name of the alarm in the Alarms widget to go to the Alarm Definitions page of the Monitoring service and view more information regarding the alarm. Note that as prerequisites to monitoring alarms in the Alarms widgets, you must have the required Monitoring service permissions and should have created alarms to be notified when a threshold is breached. For more information, see Perform Dashboard Prerequisite Tasks.