Oracle Cloud Infrastructure Documentation

Recent Changes in the Existing Features

This document enlists the recent changes in the behavior of the existing features in Oracle Log Analytics:

Topics:

  • Update Your Object Collection Rule to Use Stream:

    Starting June 1st, 2026, Oracle Log Analytics will support object collection only through stream. If you have active object collection rules in your tenancies/compartments, then update them to use stream. See Update Your Object Collection Rule to Use Stream.

  • Policy Changes for Logs Ingested Through Service Connector:

    The policies based on Service Principal will not be supported soon in Oracle Log Analytics. All new entities must be created with policies based on Virtual Resource Principal. Ensure that you complete the below policy updates soon. For a brief transition period, both Service Principal and Virtual Resource Principal based policies are supported.

    If you have policies in one of the following formats for Oracle Log Analytics service to automatically create entities when ingesting logs through Service Connector from the specific resources: 

    • allow service loganalytics to {RESOURCE_TYPE_READ} in compartment <specify_compartment>
    • allow service loganalytics to read {RESOURCE_TYPE} in compartment <specify_compartment>

    then, replace them with policies in one of the following formats to allow Oracle Log Analytics virtual resource to automatically create entities when ingesting logs from the specific resources through Service Connector: 

    • allow resource loganalyticsvrp LogAnalyticsVirtualResource to {RESOURCE_TYPE_READ} in compartment <specify_compartment>
    • allow resource loganalyticsvrp LogAnalyticsVirtualResource to read {RESOURCE_TYPE} in compartment <specify_compartment>
    Note

    • If your Service Principal policies are granted at the tenancy level, then the Virtual Resource Principal policies also must be updated for tenancy level permission.
    • In some cases, the Service Principal based policies may have been automatically created for you as part of the onboarding process or other flows. Update them to use the Virtual Resource Principal instead.

  • Oracle Logging Analytics is now Oracle Log Analytics:

    Starting July 17th, 2025, the service Oracle Logging Analytics is renamed to Oracle Log Analytics. This change reflects in all aspects of the service except the following:

    • Service metrics namespace continues to be oci_logging_analytics.
    • Service Connector target continues to be Logging Analytics.

  • Migration of Object Collection flow from Service Principal to Resource Principal:

    Oracle Log Analytics uses Service Principal to access your object storage buckets when you configure an object collection rule for continuous log collection from object storage. Starting May 30th, 2025, Oracle Log Analytics is moving to Resource Principal based authentication to access your object storage buckets. If you have active object collection rules in your tenancies/compartments, then migrate the corresponding policies from Service Principal to Resource Principal by May 30th, 2026. See Migrate Object Collection Workflow from Service Principal to Resource Principal.

    Also, Oracle Log Analytics now has a modified approach for enabling object collection from an object storage bucket which requires additional configuration while creating the object collection rule. This won't impact any of the existing object collection rules and they may be used until updates are required to the existing rules. Oracle recommends that you review active object collection rules and adapt the newer approach, as applicable. See Collect Logs from Your OCI Object Storage Bucket.

  • Dimension name in ingest-time rule:

    Starting June 1st, 2024, for the new ingest-time rules created, the dimension names posted to the OCI Monitoring service are the display names of the fields. However, for the ingest-time rules created prior to June 1st, 2024, the dimension names will continue to be the internal names of the fields.

    If the display name has a space character, then it is replaced by _ in the dimension name since the space character is not supported by OCI Monitoring Service. For example, if the display name of the field is Entity Type, then the dimension is displayed as Entity_Type in the OCI Monitoring service menu.

  • Identity domain value for OCI Audit Logs:

    The identity domain value was earlier stored in the field Domain for OCI Audit Logs. This is now changed to the field Identity Domain.