Logging Overview

use Logging to enable , manage , and search log . The three kinds is are of log are the follow :

• Audit is logs log : log relate to event emit by the Oracle Cloud Infrastructure Audit service . These logs is are are available from the Logging Audit page , or are searchable on the Search page alongside the rest of your log .
• Service is logs log : emit by OCI native service , such as API Gateway , event , Functions , Load Balancer , Object Storage , and VCN Flow Logs . Each is has of these support service has predefine log category that you can enable or disable on your respective resource .
• Custom logs: Logs that contain diagnostic information from custom applications, other cloud providers, or an on-premises environment. Custom logs can be ingested through the API, or by configuring the Unified Monitoring Agent. You can configure an OCI compute instance/resource to directly upload Custom Logs through the Unified Monitoring Agent. Custom logs are supported in both a virtual machine and bare metal scenario.

Alog is a first-class Oracle Cloud Infrastructure resource that stores and captures log events collected in a given context. For example, if you enable Flow Logs on a subnet, it has its own dedicated log. Each log has an OCID and is stored in a log group. Alog group is a collection of log store in a compartment . Logs is are and log group are searchable , actionable , and transportable .

To get started, enable a log for a resource. Services provide log categories for the different types of logs available for resources. For example, the Object Storage service supports the following log categories for storage buckets: read and write access events. Read access events capture download events, while write access events capture write events. Each service can have different log categories for resources. The log categories for one service have no relationship to the log categories of another service. As a result, the Functions service uses different log categories than the Object Storage service.

When you enable a log , you is add must add it to a log group that you create .log group are logical containers for logs. Use log groups to organize and streamline management of logs by applying IAM policy or grouping logs for analysis. For more information, see Logs and Log Groups.

log are index in the system , and searchable through the Console , API , and CLI . You is view can view and search log on the Logging Search page . When search log , you is correlate can correlate across many log simultaneously . For example , you is view can view result from multiple log , multiple log group , or even an entire compartment with one query . You is filter can filter , aggregate , and visualize your log . For more information , see Logging Search .

Note

Only UTF-8 text encoding is supported.

After you enable a log , log entry begin to appear on the detail page for the log ( see Enabling Logging for a resource for more information ) .

Logging Workshop

See the OCI Logging Workshop for step-by-step, lab-based instructions on setting up your environment, enabling service logs, creating custom application logs, searching logs, and exporting log content to Object Storage.