OCI

OCI Logging

Oracle Cloud Infrastructure (OCI) Logging is a fully managed, highly scalable service that centralizes log collection and access across your tenancy. It provides a single, consistent view of logs generated by OCI resources, capturing critical diagnostic and operational details about resource performance and access activity to support monitoring, troubleshooting, and security investigations.

How OCI Logging Works for Oracle Database@AWS Resources

Audit Logs

For Oracle Database@AWS, the OCI Audit service automatically captures calls to supported OCI public API endpoints as audit log events, providing a reliable record of administrative and operational activity in the OCI layer that supports your deployment.

Audit logging applies across OCI services (with Object Storage logging focused on bucket-related events rather than individual object events) and includes actions initiated through the OCI Console, CLI, SDKs, custom clients, or other OCI services. Each audit event records details such as the time of the activity, the source that initiated it, the target resource, the action performed, and the response returned, along with identifiers, timestamps, and request/response parameters. You can access OCI Audit events through the OCI Console or via API/SDK, and use them for troubleshooting, usage tracking, compliance reporting, and security investigations.

On the Audit page, you can explore audit logs. Audit logs are also searchable on the Search page, and you can view Audit logs in every compartment by selecting the /_Audit log group on the Search page.

Audit logs are retained for 365 days. You can view the log retention period in the tenancy details page. For more information, see Viewing Tenancy Details. Retention period is a tenancy-level setting. The value of the retention period setting affects all regions and all compartments. The retention period cannot be changed.

Viewing the Audit Logs

1. From the OCI Console, open the navigation menu.
2. Select Observability & Management. Under Logging, select Audit. The list of audit log events for the current compartment is displayed.
3. Select the Compartment that you have a permission to view.
4. Under User, add user filters. You can select multiple users.
5. Under Resource, add one or more resource filters. You can select multiple resources.
6. Under Request action types, choose one or more API operations to filter on the following:
   • GET
   • POST
   • PUT
   • PATCH
   • DELETE
7. Under Event type, you can select one or more event type filters.
8. Under Custom filters, start typing to see matching filter fields and operators, then select (or continue typing) the filter you want. This action functions the same as this field on the Logging Search page.
   Note
   
   If you want to find log events with a specific status code, put the code in quotes ("). For example: "404" to avoid partial matches.
9. Under Filter by time, you can select a preset range.
   • Past 5 minutes (the default)
   • Past 15 minutes
   • Past hour
   • Past 3 hours
   • Today
   • Custom (choose your own using the Start Date and End Date fields)
   Note
   
   Custom time ranges are limited to 14 days.
10. Select the Apply button to run the search and refresh results.
    Note
    
    The page refreshes as you adjust filters, but if time passes and new events arrive, select the Apply button again to reload results.

Exploring the Details of Events

On the Explore events tab, audit log entries are listed with key fields such as Event time, User, Resource, ActionType, and Status. Select an entry to expand it and view the full event payload in a JSON view (similar to the Logging > Search experience), where you can expand and collapse nodes and use the copy icon to copy the JSON to your clipboard. To export results, select Export log data (JSON) to download the displayed audit log data as a JSON file.

Viewing the Activity Stream

Use the Activity stream tab to view audit events in a chronological, visual list (newest to oldest). Select an event to expand and review the JSON details, and use the copy icon to copy the event content to the clipboard.

Service Logs

In Oracle Database@AWS, a service log is an OCI Logging resource used to collect and store log events for a specific context in your environment. For example, if you enable VCN Flow Logs for a subnet that supports database connectivity, OCI creates a dedicated log for that flow-log source. Each log has a unique OCID and is stored within a log group. A log group is a logical collection of logs created in a specific compartment, helping you organize logs by application, environment (development, test, and production) or operational function. Logs and log groups are searchable and can be used for analysis and operational actions. To get started, you enable logging on a resource associated with your Oracle Database@AWS deployment (for example, enabling a supported service log category such as VCN Flow Logs). OCI services expose predefined log categories that represent the types of events they can emit, and these categories are specific to each service (categories in one service don’t map to another).

Enable Logging

1. From the OCI Console, open the navigation menu.
2. Select Observability & Management. Under Logging, select Logs.
3. Select the compartment you have permission to work in.
4. Under Actions, select the Enable service log option. The Enable resource log panel opens.
   1. The Resource compartment field populates with a value.
   2. From the Service dropdown list, select a service that you want to enable logging for.
   3. From the Resource dropdown list, select a resource that you want to enable logging for.
   4. From the Configure log section, choose the Log category and enter a descriptive name in the Log name field.
   5. If you want, you can enable the Enable auto archiving to object storage (legacy) toggle.
   6. From the Advanced options section, you can manage Log location, Log retention, and Tags.
   7. Review your information and then select the Enable button to enable resource log.
   

Details for Autonomous AI Database on Dedicated Exadata Infrastructure Logs

Log Categories

Details for VCN Flow Logs

Log Categories

Check Logs

1. From the OCI Console, open the navigation menu.
2. Select Observability & Management. Under Logging, select Logs.
3. Select the compartment that contains the log group that you want to check for logs.
4. Select the Log you want to view.
5. Select the Explore log tab to see the log entries.
6. You can set the Time range field and add filters to narrow results.

Oracle Log Analytics for Oracle Database@AWS provides a cloud-based capability in Oracle Cloud Infrastructure (OCI) to centralize and use log data across a multicloud deployment. It enables you to ingest and index logs from database-adjacent components and supporting infrastructure (in AWS, OCI), then enrich, aggregate, search, and correlate events to accelerate troubleshooting and root-cause analysis. With built-in tools to visualize and monitor log trends and anomalies, Oracle Log Analytics helps improve operational visibility, performance monitoring, and security investigations for Oracle Database@AWS.

Enable Log Analytics

Create Log Groups to Store Your Logs

You can create at least one Log Group to store the logs you collect in Oracle Log Analytics. Log groups live in a specific compartment, which is how you control user access to the logs within that group. Access is managed at the compartment level, users with access to a compartment can generally access all log groups in that compartment so place log groups in compartments that align with your segregation-of-duties requirements. If those requirements change, you can move a log group to a different compartment.

Setup OCI Service Connector Import Service Logs to the Log Group in Oracle Log Analytics

View Logs in Oracle Log Analytics for Oracle Database@AWS

1. From the OCI Console, open the navigation menu.
2. Select Observability & Management, and then select Log Explorer that is located under Log Analytics.
3. Choose the Time range.
   • Last 15 minutes
   • Last 24 hours
   • Custom
4. Use one of these ways to view data:
   • Search and Query: Enter the keywords or field-based filters and then run the search.
   • Source Selection: Filter by specific log sources and Add to search. For example, Audit, VCN Flow Logs, or custom ingested sources.
   • From the Visualizations field, select Records with Histogram.
5. Select a result row to open the event details and expand fields to view the full context.

Note

If you don’t see any results, confirm:

• Log Analytics is enabled in the region.
• Logs are being ingested (sources/agents configured).
• You are searching the correct compartment/log group and time range.

Use LoganAI in Oracle Log Analytics.

LoganAI is the artificial intelligence capability in Oracle Log Analytics that helps you analyze logs and log-derived data using AI. It can also pull OCI Monitoring metrics by using MQL and combine them with log data to support richer, context-aware analysis.

LoganAI uses meta-llama or cohere model based on the selected region and availability of the model in that region. The exact regions in which LoganAI is currently available are listed in the menu when you enable LoganAI through the Configure LoganAI settings dialog box. For the regions in which Oracle Generative AI service is available, see regions.

Enable LoganAI

1. From the OCI Console, open the navigation menu.
2. Select Observability & Management, and then select Log Analytics.
3. From the left menu, select Administration, and then select Service Details.
4. Scroll down to the LoganAI field to view the status.
5. To enable LoganAI, select the Configure LoganAI settings button.
6. In the dialog, under Do you want to enable LoganAI for this tenancy?, choose the Yes option.
7. Select the Generative AI Service region you want to use. LoganAI sends log data from your current region to the selected Generative AI region for processing.
8. Under Default compartment for Generative AI Service, select the compartment used to access the Generative AI service. This must match the compartment referenced in the IAM policies for LoganAI, and users must have Generative AI access in this compartment.
9. Accept the licenses: Review and accept any required model licenses, then select the I confirm that I have reviewed and accepted all required licenses for OCI Generative AI checkbox.
   Note
   
   Model and license requirements can vary by region.
10. Under License acceptance requirements for users, choose how license acceptance is handled for other LoganAI users:
    • I will accept the license terms on behalf of all users, or
    • All users must accept the license the first time they use LoganAI, or
    • All users must accept the license once per session
11. Under Validate Settings, select the Test button to confirm connectivity to the Generative AI Service. If the test fails, resolve the issue and retest. For more information, see Troubleshoot LoganAI Issues.
12. Select the Update LoganAI settings to save and apply the configuration.

The Explain feature in LoganAI uses artificial intelligence to summarize and interpret log messages and certain charts in Log Explorer. To use it, select the AI icon wherever it appears in Log Explorer visualizations that display or tabulate log records.

LoganAI Explain is available in these modes:

• Single Log Explain: Select the AI icon on an individual log record to get an explanation of that record and ask follow-up questions.
• Multi-log Explain: Select the AI icon above the log records list to generate an explanation across the current set of log messages.
• Cluster Explain: In the Cluster visualization, select the AI icon on a cluster tab to analyze and summarize cluster patterns.
• Chart Explain: For AI-enabled charts, select the AI icon below the chart to get an explanation of what the chart indicates.

Management Dashboard lets you build performance monitoring, diagnosis, and data analysis solutions for Oracle Database@AWS resources, using powerful visualization options to gather real-time and historical data and display it in widgets. It provides Oracle-defined dashboards, widgets, and filters for common monitoring scenarios, as well as the ability to create custom dashboards and widgets to meet specific needs.

Create a Dashboard

1. From the OCI Console, open the navigation menu.
2. Navigate to Dashboards located under Home.
3. Select the New dashboard button.
4. Choose how to create it:
   • Start from a template: This option enables you choose from a collection of dashboards and templates are populated with preconfigured widgets that you can modify as needed.
   • Build from scratch: This option enables you start with an empty dashboard which you must choose which widgets to add and configure.
5. In the Create new dashboard panel, enter the following information:
   1. Enter a name in the Dashboard name field. The name can be up to 100 characters. It must not include the following characters: <>()=/'"&\
   2. The Description is optional field.
   3. Select the Compartment where the dashboard resides in.
   4. Select an existing group or create a new one for Dashboard group.
   5. Select Show additional options to add tags. This step is optional.
   6. Select the Create button.
6. Once the creation of a blank dashboard is complete, select the + Add widget button.
7. In the Add new widget window , choose the Monitoring widget.
8. In the dashboard widget, select Configure to open the Configure Monitoring widget dialog.
   1. Under Set visualization parameters, configure the following:
      1. Enter a Name for the widget.
      2. Enter a Description. This step is optional.
      3. Chart type: Select Line Chart.
      4. Interval: Select the interval for how often the chart refreshes.
      5. Filter by time: Select the time window shown in the chart.
   2. Under Configure metric query, specify the following:
      1. Select the Region.
      2. Select Change Compartment to use a different compartment. This step is optional.
      3. Select the Namespace. You can select the service or application creating the metric.
      4. Select the Metric Name . Select one metric per widget as options depend on compartment or namespace.
      5. Select the Statistic. It is an aggregation function for the metric data.
   3. In Metric Settings, you can filter using dimensions. This step is optional.
      1. Dimension Name. For example, resourceName.
      2. Dimension Value. For example, the OCID or resource identifier
      3. Use + Additional Dimension to add filters. You can use Remove (x) to delete one.
   4. Select the Configure button to save your changes.
9. Repeat step 7 and 8 to add more widgets. You can add as many as metrics you want.
10. Click on Save.

Managing Alarms in OCI Monitoring

OCI alarms let you automatically detect when a metric crosses a defined threshold and trigger an action (for example, send a notification, run an automation, or open an incident workflow). Effective alarm management includes creating alarms for critical metrics, keeping alarm rules up to date as systems change, suppressing alarms during planned maintenance to reduce noise, and deleting alarms that are no longer relevant.

Create a threshold alarm in OCI Monitoring to send a notification when a metric crosses a specified threshold. For example, the following alarm triggers when average CPU utilization over a 1‑minute interval exceeds 80%: CpuUtilization[1m].mean() > 80

On the Create Alarm page, the metric chart displays a dashed red line representing the threshold (80%). When a data point exceeds that line, the alarm transitions to a firing state and sends the configured notification.

For more information, see Best Practices for Your Alarms.