Policies Created While Onboarding Log Analytics

As a new user, if you want to start using Oracle Log Analytics, then from OCI console menu, navigate to Observability & Management, click Log Analytics, and click Start Using Log Analytics in the on-boarding page. The wizard automatically creates policies for enabling Oracle Log Analytics and configuring OCI Audit Logs collection.

The following policies are created:

  • logging_analytics_automatic_service_policies

    This policy is for enabling Oracle Log Analytics and includes the following statements:

    define tenancy sampledata as <sampledata_tenancy_OCID>
    endorse group Administrators to read loganalytics-features-family in tenancy sampledata
    endorse group Administrators to read loganalytics-resources-family in tenancy sampledata
    endorse group Administrators to read compartments in tenancy sampledata
    allow service loganalytics to READ loganalytics-features-family in tenancy
    allow service loganalytics to READ compartments in tenancy
  • logging_analytics_automatic_ingestion_policies

    The policy is for configuring OCI Audit Logs collection and includes the following statements:

    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {EVENTRULE_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {LOAD_BALANCER_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {BUCKET_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to read functions-family in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to read api-gateway-family in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {VNIC_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {APPROVED_SENDER_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {IPSEC_CONNECTION_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {WEB_APP_FIREWALL_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to read operator-control-family in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {NETWORK_FIREWALL_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {DEVOPS_DEPLOYMENT_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {DEVOPS_DEPLOY_PIPELINE_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {DEVOPS_DEPLOY_STAGE_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {APM_DOMAIN_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {SERVICE_CONNECTOR_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {DATAFLOW_APPLICATION_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {MEDIA_WORKFLOW_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {MEDIA_WORKFLOW_JOB_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {CLUSTER_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {GOLDENGATE_DEPLOYMENT_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {CG_DATA_SOURCE_READ} in tenancy
    allow resource loganalyticsvrp LogAnalyticsVirtualResource to {POSTGRES_DB_SYSTEM_READ} in tenancy
    allow any-user to {LOG_ANALYTICS_LOG_GROUP_UPLOAD_LOGS} in compartment id <compartment_OCID> where all {request.principal.type='serviceconnector', target.loganalytics-log-group.id='<target_log_group_OCID>',request.principal.compartment.id='<compartment_OCID>'}