Ingest Logs

You can load your logs into Oracle Cloud Logging Analytics using the Oracle Management Agent, uploading logs on-demand, collecting them from OCI Object Store, or using Service Connector.

Ensure to complete the prerequisites for configuring Oracle Cloud Logging Analytics. The permissions required to ingest logs are detailed in the corresponding section depending on the method of ingestion you select.

Typically, you would select one of these methods depending on your use case and how you are able to access the logs:

  • Set Up Continuous Log Collection From Your Hosts

    Install Management Agents on your on-premises hosts to continuously collect logs in Oracle Cloud Logging Analytics. This is a one-time setup.

    There are multiple ways to set up continuous log collection from your hosts:

    • Database: Collect logs stored in
      • Tables inside of an on-premises database like Oracle Database Instance, Oracle Pluggable Database, Microsoft SQL Server Database Instance, and MySQL Database Instance. See Set Up Database Instance Monitoring.
      • Tables or views of Oracle Autonomous Database. See Collect Logs from Tables or Views in Oracle Autonomous Database (Tutorial icon Tutorial ).
    • System Event Messages (Syslog): See Set Up Syslog Monitoring.
    • File: For collecting most types of logs, such as Application, and Infrastructure logs.
    • Oracle Diagnostic Log (ODL): There are typically the diagnostic logs for Oracle Fusion Middleware and Oracle Applications.
    • Windows Event Messages: All historic Windows Event Log entries as well as custom event channels.

    For more information about creating a source for collecting File, ODL, and Windows event messages, see Create a Source. Note the overall workflow for log collection in case of syslog logs to familiarize yourself with the typical steps.

  • Upload Logs on Demand

    This is useful when you have log data from old applications that aren’t supported by the Oracle Management Agent or you want to load a log file a single time to analyze them.

  • Collect Logs from Your OCI Object Storage Bucket

    You can continuously collect log data that you have stored in an Oracle Cloud Object Store bucket.

  • Ingest Logs from Other OCI Services Using Service Connector

    Use the Service Connector to identify your Oracle Cloud Infrastructure service as the source of the logs and Oracle Cloud Logging Analytics as the destination and enable the log collection.

  • Harvest Entity Model Data from Enterprise Manager Cloud Control and Collect Logs

    If you are an existing user of EMCC, then you can set up the EM Bridge and benefit from the automated set up that imports their entity model data like the entity associations, and properties information from EMCC into Oracle Cloud Logging Analytics. The entity association information is then used to construct the topology in Oracle Cloud Logging Analytics. To collect your logs from your targets in EMCC, follow the steps described.

  • Ingest Logs to OCI Logging Analytics Using Fluentd

    Use the open source data collector software, Fluentd to collect log data from your source. Install the OCI Logging Analytics Output Plugin to route the collected log data to Oracle Cloud Logging Analytics.


    Oracle strongly recommends that you use Oracle Cloud Management Agents for the best experience of ingesting log data into Oracle Cloud Logging Analytics. However, if that is not a possible option for your use case, only then use the OCI Logging Analytics Output Plugin for Fluentd.

To detect and troubleshoot the processing errors during ingestion, see Troubleshoot Ingestion Pipeline.