OCI Observability & Management

Q: What is  OCI Log Explorer

Oracle Cloud Infrastructure Log Analytics Quick Start Guide

Analyze Sample Logs with OCI Logging Analytics Hands-on Lab

OCI LOG explorer with example exacc and interview question and answer with use case - Google Search

Oracle Cloud Infrastructure Log Analytics Quick Start Guide

 OCI Log Explorer is an interactive tool in the Oracle Cloud Infrastructure Console used to search, query, filter, and visualize log data collected by OCI Logging Analytics.

Key Features

Query Bar: Write, edit, and run queries using an easy-to-learn log query language.
Visualizations: View log data through charts, histograms, cluster analysis, and data links.
Fields Panel: Drag and drop fields or click values to instantly filter logs.
Save and Export: Save frequently used searches as widgets and add them to custom dashboards. 

How to Access

Log in to the OCI Console.
Open the navigation menu in the upper left.
Select Observability & Management.
Under Logging Analytics, click Log Explore

or

Oracle Cloud Infrastructure (OCI) Log Explorer is the interactive analysis interface inside OCI Logging Analytics used to query, filter, cluster, and visualize operational log data.

---

Use Case: Troubleshooting Exadata Cloud@Customer (ExaCC) Alert & Cell Logs

The Scenario: An application running on an Exadata Cloud@Customer (ExaCC) rack reports sudden intermittent SQL latency and connection drops.
The Goal: Use Log Explorer to correlate database alert logs (alert.log) with Exadata Storage Cell logs (cellsrv.log) to check for offload bottlenecks or hardware alerts without manually SSHing into individual domU/dom0 nodes.

---

Example Log Explorer Query & Walkthrough

To find critical storage cell issues or database errors across your ExaCC infrastructure, navigate to Observability & Management > Logging Analytics > Log Explorer and run a query using the Log Analytics Query Language (LAQL):

Sample Query

laql

'Log Source' in ('Database Alert Logs', 'Exadata Storage Cell Alert Logs') 
| eval Severity = if(not core:contains(Message, 'ORA-'), 'Info', 'Critical') 
| sort -Time

What this query does:

Filters records coming from both the database tier and the ExaCC storage server cells.
Evaluates messages dynamically to tag database errors (like ORA- exceptions) as Critical.
Visualizes the output using a timeline histogram to see when error spikes happened concurrently across storage and compute.

Q1: What is the primary difference between OCI Logging and OCI Logging Analytics (Log Explorer)?

Answer: OCI Logging is a native, centralized service for ingesting and storing generic service, audit, and custom logs. Logging Analytics (Log Explorer) is an advanced operational tool built on top of that data layer that adds machine learning clustering, out-of-the-box parsers for complex enterprise applications (like Oracle Databases and Exadata), entity-labeling, and pattern outlier detection.

Q2: How do you collect diagnostic logs from an ExaCC (Exadata Cloud@Customer) environment into Log Explorer?

Answer: You deploy and configure the OCI Management Agent on the database domU/hosts and storage cell management networks. The agent actively monitors target log file paths (e.g., alert logs, trace files, cell diagnostics) and pushes them securely into the Logging Analytics workspace.

Q3: How does the | link operator assist in troubleshooting complex multi-tiered systems like Exadata?

Answer: The | link command is an unsupervised machine learning feature in Log Explorer that groups correlated log entries across disparate data sources based on shared attributes (such as resource name, IP, or transaction ID), letting you trace a performance bottleneck spanning both database instances and storage cells simultaneously.

Q1: What is the primary difference between standard OCI Logging Search and OCI Logging Analytics Log Explorer?

Answer: Standard OCI Logging Search provides basic keyword search and tailing for native service, audit, and custom logs. Log Explorer (part of Logging Analytics) offers advanced machine learning capabilities—such as pattern clustering, anomaly detection (outliers), custom parsers, and interactive field-value aggregations across multi-cloud or hybrid data sources.

Q2: How does the "Cluster" feature inside Log Explorer help during an incident?

Answer: Clustering uses unsupervised machine learning to group thousands of noisy log records into unique, recognizable patterns. It instantly highlights Potential Issues (errors/exceptions), Outliers (events happening only once), and Trends, reducing troubleshooting time from hours to minutes.

Q3: How do you route custom logs from OCI Compute or external sources into Log Explorer?

Answer: You install the Management Agent on compute instances or use a Service Connector Hub to stream custom application logs from the native OCI Logging service into Logging Analytics, where a designated Parser parses the payload.