Ingest Logs

You can load your logs into Oracle Log 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 Log 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:

Log Collection Method	Description	More Information
Set Up Continuous Log Collection From Your Hosts Based on your source type, you can follow specific workflow too: File System Event Messages (Syslog) Database REST API Windows Event Messages Oracle Diagnostic Logs (ODL)	Install Management Agents on your on-premises hosts to continuously collect logs in Oracle Log Analytics. This is a one-time setup. File: For collecting most types of logs, such as Application, and Infrastructure logs. System Event Messages (Syslog) Database: Collect logs stored in tables and views of a database like Oracle Database Instance, Oracle Pluggable Database, Oracle Autonomous Database, Microsoft SQL Server Database Instance, and MySQL Database Instance. REST API: PULL logs periodically from the log endpoint provided by you through REST API calls. Windows Event Messages: All historic Windows Event Log entries as well as custom event channels. Oracle Diagnostic Logs (ODL): These are typically the diagnostic logs for Oracle Fusion Middleware and Oracle Applications.	Set Up Continuous Log Collection From Your Hosts File: Ingest Application, Infrastructure, Database and Other Generic Logs System Event Messages (Syslog): Set Up Syslog Monitoring. Database: Set Up Database Instance Monitoring. For specific details about the database support, see: Oracle Database Microsoft SQL Server Database Instance MySQL Database Instance REST API: Set Up REST API Log Collection. Windows Event Messages: Set Up Windows Event Monitoring. Oracle Diagnostic Logs (ODL): Ingest Logs of Oracle Diagnostic Logging (ODL) Format.
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.	Upload Logs on Demand
Upload Event Logs Using LogEvents API	Use the LogEvents API to PUSH logs from your log-emitting host to Oracle Log Analytics through an Oracle-provided endpoint.	Upload Event Logs Using LogEvents API
Collect Logs from Your Object Storage Bucket	You can continuously collect log data that you have stored in an Oracle Cloud Object Store bucket.	Collect Logs from Your OCI Object Storage 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 Log Analytics as the destination and enable the log collection.	Ingest Logs from Other OCI Services Using Service Connector
Ingest Custom Logs from OCI Logging Service Using Service Connector	If you have custom logs in OCI Logging service for which Oracle-defined parsers and sources are not available, then you can create your own parser and source. Create a service connector to establish connection with OCI Logging service and enable collection of your custom logs in Oracle Log Analytics.	Ingest Custom Logs from OCI Logging Service Using Service Connector
Ingest Custom Logs from OCI Streaming Service Using Service Connector	If you want to analyze and derive insights from your high-volume custom streaming data in OCI Streaming service, then create a service connector to establish connection with OCI Streaming service and enable collection of your custom logs in Oracle Log Analytics.	Ingest Custom Logs from OCI Streaming Service Using Service Connector
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 Log Analytics. The entity association information is then used to construct the topology in Oracle Log Analytics. To collect your logs from your targets in EMCC, follow the steps described.	Harvest Entity Model Data from Enterprise Manager Cloud Control and Collect Logs
Ingest Kubernetes Logs into Oracle Log Analytics	The Add Data wizard is launched from the Kubernetes Solution page. The Oracle Log Analytics Kubernetes Monitoring Solution offers a comprehensive user interface to monitor the various components of the Kubernetes deployments.	Kubernetes Monitoring Solution
Auto-Discovery of Entities and Log Collection	Initiate the discovery of entities like packaged applications, databases, middleware, and other components using the Stack Monitoring UI, collect logs from those entities, and view the entity topology.	Auto-Discovery of Entities and Log Collection

To ingest logs using a wizard in the console, see Use Add Data Wizard for Ingesting Logs.

To detect and troubleshoot the processing errors, see Troubleshoot Ingestion Pipeline and Troubleshoot Log Processing Pipeline.

For some of the Oracle-defined solutions that cover end-to-end process for collecting logs from different applications, platforms, and infrastructure, see table Solutions and Marketplace Apps in Technical Resources at Your Finger Tips.

Use Add Data Wizard for Ingesting Logs

The Add Data wizard available in the Administration page of Log Analytics offers a ready interface to ingest logs through any of the following methods. Click Add Data on the Administration Overview page, expand the corresponding section in the Add Data page, and follow the guidelines in the wizard to ingest the logs. For more details about each of these ingestion methods, the required IAM policies, and step-by-step instructions to ingest logs without the wizard, follow the corresponding links below:

Monitor OCI resources: Ingest Logs from Other OCI Services Using Service Connector
Monitor with management agent: Set Up Continuous Log Collection From Your Hosts
Monitor Kubernetes: Kubernetes Monitoring Solution
Security and Compliance: Ingest Logs from Other OCI Services Using Service Connector
Advanced collection methods: Upload Logs on Demand

Note

When using Add Data wizard, you must be a member of the Administrators group with access to root compartment if you want to ingest logs using any of the following methods:

Monitor OCI resources
Monitor with management agent: Only if you must also configure the management agent
Monitor Kubernetes (recommended)
Security and Compliance

See The Administrators Group, Policy, and Administrator Roles.

For an example walk through of the steps to ingest OCI service logs using Add Data wizard, watch Video: How to Quickly Ingest Logs into Log Analytics from Other OCI Services in Oracle Cloud Observability and Management Platform.

Oracle Cloud Infrastructure Documentation

Ingest Logs