Azure Log Analytics

Azure Log Analytics provides a centralized platform to collect, analyze, and correlate logs and metrics across Oracle Database@Azure and Azure services.

Azure Log Analytics allows you to run and modify log queries against data stored in Azure Monitor Logs. It supports two modes:
  1. Simple mode: It provides a spreadsheet-like, point-and-select experience for filtering, sorting, and aggregating log data.
  2. KQL mode: It enables advanced users to use Kusto Query Language (KQL) for deeper analysis.

Azure Log Analytics is the primary tool used to build and validate queries that can be consumed interactively or integrated with other Azure Monitor features such as log-based alerts and workbooks.

Azure Log Analytics is the observability layer for Oracle Database@Azure, consolidating Oracle-managed service logs and metrics with Azure infrastructure telemetry into a single analytics platform to close operational visibility gaps.

Azure Log Analytics collects and correlates telemetry from:
  • Oracle Database@Azure
  • Azure compute/OS telemetry (VMs)

By consolidating these signals, Azure Log Analytics enables a single-pane-of-glass view across Oracle and Azure layers. Azure Monitor Logs use a central data store where Azure collects and organizes log data into tables so you can query, correlate, alert, and visualize it. This central data store is called the Azure Log Analytics workspace. For Oracle Database@Azure, it becomes the landing zone where you can bring together signals from Oracle Database components and Azure platform logs to obtain a single operational view.

Azure Log Analytics is supported with Oracle Exadata Database Service on Dedicated Infrastructure and Oracle Base Database Service.

Overview of Azure Log Analytics for Oracle Database@Azure

  1. Setup Log Analytics workspace
  2. Setup Log Analytics
    1. Set Up Log Analytics for Oracle Exadata Database Service on Dedicated Infrastructure
    2. Set Up Log Analytics for Oracle Base Database Service
  3. Monitor Data in Azure Log Analytics
  4. Create an alert directly from a log query.

Setup Log Analytics Workspace

  1. Sign in to the Azure portal.
  2. Navigate to Log Analytics workspaces.
  3. Select the Create button.
  4. In the Basics section, enter the following information:
    1. From the dropdown list, select your Subscription.
    2. From the dropdown list, select your Resource group. If you want to create a new one, select the Create new link.
    3. Enter a descriptive name for your Log Analytics workspace. The workspace name must be between 4 and 63 characters. The workspace name can contain only letters, numbers and hyphen (-). The hyphen (-) shouldn't be the first or the last symbol.
    4. Select your Region for Oracle Database@Azure.
    5. Select the Next: Tags > button.
  5. The Tags section is optional. Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups.
  6. Configure pricing/retention settings according to your organizational standards. This step is optional. You can configure these settings after creation of Log Analytics workspace as part of governance.
  7. Select the Next: Review + Create >.
  8. Select the Create button to deploy the workspace.
  9. After the workspace is created, connect data sources such as Azure resources, agents, or diagnostics settings to begin collecting logs in the workspace tables.

Set Up Log Analytics for Oracle Exadata Database Service on Dedicated Infrastructure

  1. From the Azure portal, select Oracle Database@Azure.
  2. From the left menu, select Oracle Exadata Database Service on Dedicated Infrastructure and then select Oracle Exadata VM Clusters tab.
  3. From the list, select your Oracle Exadata VM Cluster that you want to monitor.
  4. Expand the Monitoring section, and then select Diagnostics settings.
  5. Select the Add diagnostic setting button, and then enter the following information:
    1. Enter a descriptive name in the Diagnostic setting name field.
    2. Select the Category groups located under the Logs.
    3. Choose Send to Log Analytics workspace as your Destination.
      1. Select your Subscription.
      2. Select your Log Analytics workspace
      3. Choose the Destination table. Select which table resource data is stored in.
    4. Select the Save button to save your information.

Set Up Log Analytics for Oracle Base Database Service

  1. From the Azure portal, select Oracle Database@Azure.
  2. From the left menu, select Oracle Base Database Service.
  3. From the list, select your Base Database that you want to monitor.
  4. Expand the Monitoring section, and then select Diagnostics settings.
  5. Select the Add diagnostic setting button, and then enter the following information:
    1. Enter a descriptive name in the Diagnostic setting name field.
    2. Select the Category groups located under the Logs.
    3. Choose Send to Log Analytics workspace as your Destination.
      1. Select your Subscription.
      2. Select your Log Analytics workspace
      3. Choose the Destination table. Select which table resource data is stored in.
    4. Select the Save button to save your information.

Monitor Data in Azure Log Analytics

  1. From the Azure portal, navigate to Log Analytics workspaces.
  2. From the list, select the workspace that you want to view.
  3. From the left menu, select Logs. This opens the Log Analytics query editor.
  4. Select the tables you want to query.
  5. Explore Data (Simple mode)
      • By default, you can see the Simple mode, which provides a spreadsheet-like experience.
      • Use point-and-Select filters, sorting, and aggregation to explore available log data.
      • Ideal for quick checks such as recent errors, activity logs, or resource health events.
    Note

    Few metrics, such as CPU Utilization, can appear multiple times with different labels. For example, CPU Utilization (OCI Database Cluster), CPU Utilization (OCI Database), and CPU Utilization (Oracle OCI Database).
    • OCI Database Cluster is for the VM Cluster metrics.
    • OCI Database is for the Container Database metrics.
    • Oracle OCI Database is for the Pluggable Database metrics.
    This screenshot shows how to monitor logs.
  6. Query Data Using KQL (Advanced Mode)
    1. From the dropdown, switch the mode to KQL mode.
    2. Browse available tables shown on the left side. For example:
      AzureMetrics, OracleCloudDatabase, Usage

      For more information, see the table reference AzureMetrics, OracleCloudDatabase, and Usage.

    3. Run a basic query. For example:
      1. The following query lists CPU Utilization Metrics of all resources in the Exadata Infrastructure which includes VM cluster, Container Database and Pluggable Database.
        search in (AzureMetrics) "CpuUtilization" | take 100
      2. The following query lists CPU Utilization Metrics of all Container Databases.
        search in (AzureMetrics) "oci_database/CpuUtilization" | take 100
      3. The following query lists CPU Utilization Metrics of all Pluggable Databases.
        search in (AzureMetrics) "oracle_oci_database/CpuUtilization" | take
            100
      This screenshot shows how to monitor logs.
  7. Convert query results into charts, graphs, or tables directly from the query results pane.

Create Alert Directly from a Log Query

  1. From the Azure portal, navigate to Log Analytics workspaces.
  2. From the list, select the workspace that you want to view.
  3. From the left menu, select Logs. This opens the Log Analytics query editor.
  4. Run your query and verify the results.
  5. From the Logs query window, select the ... icon and then select the + New alert rule option. From the Create an alert rule page, enter the following information.
    1. In the Scope section, the required fields are populated automatically.
    2. In the Condition section, confirm the Search Query condition and then set the following based on your requirements:
      • Measurement: Measure for the aggregation, Aggregation type, Aggregation granularity
      • Alert logic: Operator as Greater than, Threshold value and Frequency of evaluation
      This screenshot shows how to monitor logs.
    3. In the Actions section, select an existing Action group or Create a new one. For example: email/SMS/webhook/Logic App/Function. Select the Next: Details button.
    4. In the Details section,
      1. Enter Alert rule name. This is required field.
      2. The Alert rule description field is optional.
      3. Select the Region.
      4. Choose the Identity which will determine the permissions you have for accessing Azure Data Explorer and other resources when the query is running.
    5. The Tags section is optional. Tags are name and value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups.
    6. Review your information, and then select the Create button to enable alert rule.