Feature Overview (aka. Goal Summary)  

Add a flow logs exporter to the Network Observability Operator.

Goals (aka. expected user outcomes)

The Network Observability Operator must be able to plug-in to customer's OpenTelemetry-based operational data pipeline, directly, or it risks becoming an "island solution" that is not part of their production Operational Support machinery.

This development enhances the ecosystem integration capabilities of the Network Observabiltiy Operator by adding the ability to export flow logs in an OpenTelemetry format for consumption by an external OpenTelemetry collector.

Requirements (aka. Acceptance Criteria):

• A new exporter type must be created in FlowCollector CRD
• When configured, the operator must configure FLP with this collector endpoint
• The operator should also configure FLP to use otel fields format. A draft specification of this format is being discussed here: https://github.com/rhobs/observability-data-model/pull/2 . This format configuration should be done transparently by the operator, and only for the otel export (it must not affect other FLP outputs).

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Questions to Answer (Optional):

Out of Scope

Background

Customer Considerations

Documentation Considerations

Interoperability Considerations