Oracle Cloud Infrastructure Documentation

Google Cloud Audit Logs

Google Cloud Logging automatically generates audit logs that record administrative activities and access events within Google Cloud resources. Audit logs provide visibility into who performed what action, on which resource, where, and when, enabling customers to achieve the level of transparency expected in traditional on-premises environments. Audit logs are useful for security monitoring, auditing, and regulatory compliance, allowing organizations to detect misconfiguration, investigate incidents, and monitor for potential data misuse across their Google Cloud environments.

Oracle Database@Google Cloud integrates with Google Cloud Logging to provide centralized visibility into both:
  • Audit logs (who performed which action, on which resource, where, and when)
  • Resource logs (actions taken by the Oracle Database service)

These logs enable you to meet security, auditing, compliance, and operational monitoring requirements by using native Google Cloud tools.

Relevance of Database Operations in Oracle Database@Google Cloud

For Oracle Database@Google Cloud, audit logs provide the following benefits:
  • Track the creation and deletion of networks, VM clusters, Exadata Infrastructure, and peering connections.
  • Retrieve configuration information for clusters, database nodes, and ODB networks.
  • List Autonomous VM Clusters, VM clusters, database nodes, database servers, and related resources.

Monitoring Oracle Database@Google Cloud Resource Logs in Google Cloud Logging

This section explains how to view Oracle Database@Google Cloud resource logs in Google Cloud Logging using the Google Cloud Console.

  1. From the Google Cloud Console, navigate to Logs Explorer.
  2. At the top of the page, select the Google Cloud project that contains your Oracle Database@Google Cloud resources.
  3. In the query builder, select All resources.
  4. From the dropdown list, select one of the following resource types, depending on the resource you want to monitor:
      • Exadata Infrastructure
      • Cloud VM Cluster
      • Autonomous AI Database
      • Db System
      • DbSystem Container Database
      • DbSystem Pluggable Database
      • Exadb Container Database
      • ExaDB Storage Vault
      • ExaDB VM Cluster
  5. In the selection dialog, select the specific location and resource and then select the Apply button.This screenshot shows how to select resource.
  6. Select the All log names option to open the log name selector. Select one or more of the following Oracle Database@Google Cloud log files, as required and then select the Apply.
    oracledatabase.googleapis.com/autonomous_database_logs
oracledatabase.googleapis.com/container_database_logs
oracledatabase.googleapis.com/db_system_container_database_logs
oracledatabase.googleapis.com/db_system_logs
oracledatabase.googleapis.com/db_system_pluggable_database_logs
oracledatabase.googleapis.com/exadata_infrastructure_logs
oracledatabase.googleapis.com/exadb_container_database_logs
oracledatabase.googleapis.com/pluggable_database_logs
oracledatabase.googleapis.com/vm_cluster_logs
oracledatabase.googleapis.com/exascale_db_storage_vault_logs
oracledatabase.googleapis.com/exadb_vm_cluster_logs
  7. You can Filter by Severity. This step is optional but it is recommended when you want to troubleshoot or investigate issues.
    1. Select the All severities option.
    2. Select the desired log severity level. For example: INFO, WARNING, ERROR.
  8. To set the time range, select a preset time range, or create a custom time range to narrow the log results to a specific window.
  9. The Logs Explorer displays the selected Oracle Database@Google Cloud resource logs based on the chosen resource, log name, severity, and time range. You can further refine results using text search or advanced query filters.

Monitoring the Logs

Logs Explorer in the Google Cloud Console provides a centralized interface to retrieve, view, and analyze log entries stored in Google Cloud log buckets. It enables operators to examine individual log entries as well as sequences of logs to troubleshoot issues and improve overall observability.

Below is an example of Autonomous AI Database audit logs for the database_ID as jsiadmin1 located in the us-east-4 region for the last 14 days.

This screenshot shows how to monitor the logs.

In the following example, the log entry shows an API call to start Autonomous AI Database, along with the corresponding timestamp and the originating IP address.

This screenshot shows how to monitor the logs.

Additionally, to create alert policies and filter logs, you must use the Logging query language. For more information, see Unified Maintenance log schema which details the fields in the Unified Maintenance resource ResourceMaintenance. Use these fields to write query operations for Unified Maintenance resources.

To obtain explanation of the logs using Google Cloud Assist, complete the following steps:
Note

This step is optional.
  1. Expand the log entries.
  2. Select Explain this log entry. This provides a brief explanation of the particular log message.This screenshot shows how to obtain explanation of logs