Google Cloud Observability

Exadata VM Cluster Metrics

1. Obtain the Exadata VM Cluster ID.
   1. Navigate to the Oracle Database@Google Cloud Console.
   2. Select the Dedicated Infrastructure under Exadata Database Service.
   3. Select Exadata VM Clusters.
   4. Copy the Cluster ID from this page. You need this information in the Google Cloud Monitoring console.
2. View the Exadata VM Cluster metrics.
   1. Go to the Cloud Monitoring metrics explorer page in the Google Cloud console.
   2. Go to Metrics explorer
   3. In the Queries section, select Select a metric, and choose Cloud VM Cluster to view its metrics.
   4. Select an active metric and then select the Apply.
   5. Filter with “Cloud_VM_CLUSTER_ID” equals to the Cluster ID obtained from previous step.
   6. The metric is displayed. You can view your metric as a chart, table, or both by selecting the option in the results pane.

Observability metrics for Exadata VM Clusters

Exadata Container Database Metrics

1. Obtain the Exadata Container Database Name
   1. Navigate to the Oracle Database@Google Cloud Console.
   2. Select the Dedicated Infrastructure under Exadata Database Service.
   3. Select Exadata VM Clusters.
   4. Select Manage in OCI. This takes you to the Exadata VM Cluster page.
   5. Select the Databases tab and select your respective Database.
   6. From the Database Information page, you can select the OCID.
   7. Copy that as we need this information in the Google Cloud Monitoring console.
2. View the Exadata Container Database Metrics
   1. Go to the Cloud Monitoring metrics explorer page in the Google Cloud console. For more information, see Go to Metrics explorer
   2. In the Queries section, select Select a metric, and choose resource names to view metrics for that resource: Container Database. Select an active metric and then select the Apply button.
   3. Filter the same with resource_ID as the OCID of the container database.
   4. The metric is displayed. You can view your metric as a chart, table, or both by selecting the option in the results pane.

Observability metrics for Exadata Container Databases

Pluggable Database Metrics

To view the pluggable database metrics, navigate to the OCI console and enable the Database management (Diagnostics & Management) to view the metrics. Refer to this link to enable Database Management for a Pluggable Database.

Autonomous Database Metrics

1. Obtain the Autonomous Database ID
   1. Navigate to the Oracle Database@Google Cloud Console.
   2. Select the Autonomous Database under Autonomous Database Service.
   3. Select Autonomous Database you want to monitor.
   4. Copy the Database ID from this page. You need this information in the Google Cloud Monitoring console.
2. View the Autonomous Database Metrics
   1. Go to the Cloud Monitoring metrics explorer page in the Google Cloud console. For more information, see Go to Metrics explorer
   2. In the Queries section, select Select a metric, and choose resource names to view metrics for that resource: Autonomous Database.
   3. Select an active metric and then select the Apply button.
   4. Filter the same with autonomous_database_id as the Database ID of the Autonomous Database.
   5. The metric is displayed. You can view your metric as a chart, table, or bothby selecting the option in the results pane.

Observability metrics for Autonomous Databases

Base Database Metrics

1. Obtain the Information
   1. Navigate to the Oracle Database@Google Cloud Console.
   2. Select the Base Database under Base Database Service.
   3. Select the following attributes of the Base Database depending on what you want to monitor.
      1. Hostname prefix - If you want to monitor the metrics of the Node hosting the Base DB or the ExaDB VM Cluster metrics.
      2. Database Unique Name - if you want to monitor the Metrics of the Container Database
   4. Copy the above information from this page. You need this information in the Google Cloud Monitoring console.
2. View the Metrics
   1. Go to the Cloud Monitoring metrics explorer page in the Google Cloud console. Go to Metrics explorer
   2. In the Queries section, select Select a metric, and choose resource names to view metrics for that resource:
      1. DbSystem Container Database and select an active metric and the select the Apply button. Filter with instance_name. Use the Database Unique Name from above. This will show the Container Database Metrics.
      2. DbSystem and select an active metric and the select the Apply button. Filter with Hostname. Use the Hostname prefix from above. This will show the Host metrics.
   3. The metric is displayed. You can view your metric as a chart, table, or both by selecting the option in the results pane.

Observability metrics for Base Databases

Observability metrics for Base Database Systems

Pluggable Database Metrics

To view the pluggable database metrics, navigate to the OCI console and enable the Database management (Diagnostics & Management) to view the metrics. Refer to this link to enable Database Management for a Pluggable Database.

Exascale Infrastructure Metrics

1. Obtain the Information
   1. Navigate to the Oracle Database@Google Cloud Console.
   2. Select the Exascale Infrastructure under Exadata Database Service.
   3. Select and copy the Cluster ID of the VM Cluster you want to monitor . You need this information in the Google Cloud Monitoring console.
2. View the Metrics
   1. Go to the Cloud Monitoring metrics explorer page in the Google Cloud console. Go to Metrics explorer
   2. In the Queries section, select Select a metric, and choose resource names to view metrics for that resource.
      1. ExaDB VM Cluster and select an active metric and then select the Apply button. Filter with exadb_vm_cluster_id. Use the Cluster_ID copied from above. This will show the VM cluster Metrics.
      2. ExaDB Container Database and select an active metric and then select the Apply button. Filter with exadb_vm_cluster_id. Use the Cluster_ID copied from above.. This will show the Container Database metrics.
   3. The metric is displayed. You can view your metric as a chart, table, or both by selecting the option in the results pane.

Observability metrics for Exascale VM Clusters

Observability metrics for Container Databases (Exascale)

Pluggable Database Metrics

To view the pluggable database metrics, navigate to the OCI console and enable the Database management (Diagnostics & Management) to view the metrics. Refer to this link to enable Database Management for a Pluggable Database.

Build Custom Dashboard and Monitor using Google Cloud Monitoring Dashboards

Google Cloud Monitoring Dashboard for Oracle Database@Google Cloud provides a centralized, customizable view of the health, performance, and availability of Oracle workloads running in Google Cloud. By collecting telemetry data such as metrics, logs, and traces from the Oracle Database infrastructure (VM clusters, ODB networks) and the Google Cloud environment (VPCs, Compute Engine, Cloud Interconnect), the dashboard allows teams to visualize database activity, detect anomalies, and troubleshoot issues in real time.

Create a Custom Dashboard and Monitor using Google Cloud Monitoring Dashboards

1. Go to the Google Cloud Console, navigate to Observability Monitoring and select Dashboards.
2. In the Dashboards Overview page, select Create Dashboard.
3. select Add widget.
4. In the Add widget pane, select a widget to add to your dashboard. For this example, select Metric.
5. You can select a widget based on the type of data to display or how you want to display the data. In all cases, a configuration pane is opened. For example, you can select the Metric widget and then set the visualization to Stacked Or, you can select the Stacked area widget and then select the Metric.
6. In the Configure widget page, select Select a metric drop-down menu and choose one of the following resource names to view metrics for that resource: Cloud VM Cluster, Autonomous Database, Container Database, or Pluggable Database.
7. Under ACTIVE METRICS, select any metric you want to add in dashboard and select Apply.
8. Select Apply to add the widget to the dashboard. This will add the widget to the dashboard.
9. Repeat step 3 to 8 to add more widgets to the dashboard.
10. Select the dashboard name and you can rename it.
11. Go back to Dashboards Overview to see the list of dashboards.
12. Select the newly created dashboard from the list of dashboards and change the time range to Today.

Example of a custom Dashboard

In the below example, a custom dashboard name “Autonomous CPU Compare” is created to compare the CPU Utilization of few Autonomous Databases in a certain timeframe.

Configure Alert Policies and Notifications

This section describes how you can get notified when any of the metrics of your Oracle Database@Google Cloud cross defined threshold or when the performance doesn't meet defined criteria.

The Cloud Monitoring alerting process contains three parts:

• An alerting policy, which describes the circumstances under which you want to be alerted and how you want to be notified about an incident. The alerting policy can monitor time-series data stored by Monitoring or logs stored by Cloud Logging. When that data meets the alerting policy condition, Monitoring creates an incident and sends the notifications.
• Each incident is a record of the type of data that was monitored and when the conditions were met. This information can help you troubleshoot the issues that caused the incident.
• A notification channel defines how you receive notifications when Monitoring creates an incident. For example, you can configure an alerting policy to email my-suppport-team@rxample.com and to post a Slack message to the channel #my-support-team. An alerting policy can contain one or more notification channels.

Create a Notification channel

To add an email notification channel, do the following:

1. In the Google Cloud console, go to the notifications Alerting page: Go to Alerting
2. If you use the search bar to find this page, then select the result whose subheading is Monitoring.
3. In the toolbar of the Google Cloud console, select your Google Cloud project.
4. Select Edit notification channels.
5. In the Email section, select Add new.
6. Enter a single email address and a description.
7. Select Save.

If you use a group email address as the notification channel for an alerting policy, then configure the group to accept mail from alerting-noreply@google.com.

You can create alerting policies to monitor different types of data depending on your alerting needs. The following sections list the different types of data that you can monitor with alerting policies.

Monitor time series data

Create a custom alert

1. Open Alerting
   1. In the Google Cloud Console, go to Monitoring → Alerting.
   2. Select the correct Google Cloud project
   3. Select Create Policy.
2. Select a Metric
   1. Select Select a metric.
   2. Choose a resource type (e.g., Autonomous Database).
   3. Choose a metric type from Active Metrics (e.g., CPU utilization).
   4. Add filter (e.g., by resource_id or location ).
   5. Select Rolling window: Align metric values over a time window (e.g., 15 min). Select Next
3. Configure the Trigger
   1. Leave Condition type = Threshold.
   2. Define the alert threshold:
      • Example: Above 0.9 (CPU > 90%)
   3. Choose when the condition is met:
      • Any time series violates (default)
      • Percent of time series violate (e.g., 50% of nodes in cluster)
      • To specify how Monitoring evaluates the condition when data stops arriving, expand Advanced options, and then use the Evaluation missing data

        The Evaluation missing data menu is disabled when the value of the Retest window is No retest.

        Google Cloud console"Evaluation of missing data" field	Summary	Details
        Missing data empty	Open incidents stay open. New incidents aren't opened.	For conditions that are met, the condition continues to be met when data stops arriving. If an incident is open for this condition, then the incident stays open. When an incident is open and no data arrives, the auto-close timer starts after a delay of at least 15 minutes. If the timer expires, then the incident is closed. For conditions that aren't met, the condition continues to not be met when data stops arriving.
        Missing data points treated as values that violate the policy condition	Open incidents stay open. New incidents can be opened.	For conditions that are met, the condition continues to be met when data stops arriving. If an incident is open for this condition, then the incident stays open. When an incident is open and no data arrives for the auto-close duration plus 24 hours, the incident is closed. For conditions that aren't met, this setting causes the metric-threshold condition to behave like a metric-absence condition. If data doesn't arrive in the time specified by the retest window, then the condition is evaluated as met. For an alerting policy with one condition, the condition being met results in an incident being opened.
        Missing data points treated as values that don't violate the policy condition	Open incidents are closed. New incidents aren't opened.	For conditions that are met, the condition stops being met when data stops arriving. If an incident is open for this condition, then the incident is closed. For conditions that aren't met, the condition continues to not be met when data stops arriving.

4. Configure the notification and add user labels.
5. Expand the Notifications and name menu and select your notification channels created in the previous step. For redundancy purposes, we recommend that you add to an alerting policy multiple types of notification channels. For more information, see Manage notification channels.
   1. Optional: To use a custom subject line in your notification instead of the default, update the Notification subject line
   2. Optional: To be notified when an incident is closed, select Notify on incident closure. By default, when you create an alerting policy with the Google Cloud console, a notification is sent only when an incident is created.
   3. Optional: To change how long Monitoring waits before closing an incident after data stops arriving, select an option from the Incident autoclose duration By default, when data stops arriving, Monitoring waits seven days before closing an open incident.
6. Select Alert name and enter a name for the alerting policy.
7. Select Create policy.