-
Notifications
You must be signed in to change notification settings - Fork 359
Description
We are running workloads on Oracle Kubernetes Engine (OKE) and would like to use Logging Operator as the centralized logging solution.
Currently, Logging Operator does not provide built-in support for Oracle Log Analytics output plugins, and it is not possible to configure OCI Logging Analytics as a native output.
We would like Logging Operator to support Oracle OCI Log Analytics as a first-class output plugin.
This could be achieved by:
Including the Log Analytics plugin in the logging-operator output APIs.
The relevant Fluent Bit plugin documentation is available here:
https://docs.fluentbit.io/manual/data-pipeline/outputs/oci-logging-analytics#fluent-bit.yaml
With native support, users could configure OCI Logging Analytics as an output via the existing CRDs of the Output and ClusterOutput APIs.
The alternative is to use the Fluent Bit Helm chart / Oracle Kubernetes monitoring Helm chart or maintain a dedicated Helm chart that supports all the required functionality in order to interact with the Oracle Log Analytics API.
The main motivation is to be able to stream Fluent Bit logs to multiple outputs, where each one streams to a specific log group.
It would be even better to include the creation of the log group from the logging-operator side, but that is optional.
This would enhance support for application multi-tenancy.
OCI Log Analytics is a core service for users running Kubernetes on Oracle Cloud.
Native support would make Logging Operator significantly easier to adopt in OCI-based environments and improve parity with other major cloud providers.
Thanks in advance for considering this feature request.