-
Epic
-
Resolution: Done-Errata
-
Major
-
None
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
- is documented by
-
OBSDOCS-820 [DOC] Log Forwarding Natively to Azure Log Analytics
- Closed
- is duplicated by
-
LOG-5022 Native OCP Log forwarding Integration with Azure Log Analytics
- New
- links to
-
RHBA-2024:128809 Logging Subsystem 5.9.0 - Red Hat OpenShift
There are no Sub-Tasks for this issue.