Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-4605

Implement Log Forwarding to Azure Log Analytics

    XMLWordPrintable

Details

    • Azure Log Analytics LogForwarding
    • False
    • None
    • False
    • Green
    • NEW
    • Administer, API
    • To Do
    • OBSDA-225 - Native OCP Log forwarding Integration with Azure Monitor
    • OBSDA-225Native OCP Log forwarding Integration with Azure Monitor
    • NEW
    • 100
    • 100% 100%
    • Hide
      With this update, the Cluster Log Forwarder API now supports log forwarding to Azure Monitor Logs, providing users with enhanced monitoring capabilities. This feature empowers users to maintain optimal system performance and streamline log analysis processes within Azure Monitor, leading to improved operational efficiency and faster issue resolution.
      Show
      With this update, the Cluster Log Forwarder API now supports log forwarding to Azure Monitor Logs, providing users with enhanced monitoring capabilities. This feature empowers users to maintain optimal system performance and streamline log analysis processes within Azure Monitor, leading to improved operational efficiency and faster issue resolution.
    • Feature

    Description

      Goals

      • Provide an API to forward logs to Azure Log Analytics directly from collector deployments using Azure Log Analytic API

      Non-Goals

      Motivation

      The log team has a larger goal of being able to forward logs to the platform log solution for all platform providers (e.g. AWS, GCP). Additionally, customers also desire this feature without needing to provide an intermediate service. It is currently possible to forward to ALA using a kafka bus.

      Alternatives

      • Admins configure a kafka endpoint and utilize kafka for logs

      Acceptance Criteria

      • Verify logs can be forwarded to an Azure Log Analytics endpoint

      Risk and Assumptions

      • Assumption: Vector supports ALA
      • Risk: Vector does not support short-lived tokens

      Documentation Considerations

      • Feature Announcment (release note)?
      • API Changes
      • Feature usage

      Open Questions

      • Does vector support short lived tokens for ALA
      • How do we integrate STS worflows when forwarding to ALA
      • How do we functionally test forwarding to ALA
        • Can we set-up CI specifically for Azure Log?
        • Are there mocks available?

      Additional Notes

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. OBSDOCS-820 [DOC] Log Forwarding Natively to Azure Log Analytics

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is duplicated by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-5022 Native OCP Log forwarding Integration with Azure Log Analytics

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • New
          links to

          GitHub openshift/openshift-docs#73530: [DOCS] OBSDOCS-833 Logging 5.9.0 Release Notes

          Web Link RHBA-2024:128809 Logging Subsystem 5.9.0 - Red Hat OpenShift

          Activity

            People

              vparfono Vitalii Parfonov
              jcantril@redhat.com Jeffrey Cantrill
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: