• Icon: Epic Epic
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • netobserv-1.4
    • None
    • None
    • None
    • netobserv-ipfix-exporter
    • BU Product Work
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-357 - Add IPFIX Exporter to the Network Observability Operator
    • OCPSTRAT-357Add IPFIX Exporter to the Network Observability Operator
    • 0% To Do, 0% In Progress, 100% Done
    • S

      Similar to our Kafka exporter, we can have an IPFIX exporter, configured via the CRD, that exports enriched flows to any IPFIX collector.

      This feature must not be confused with the Agent type, which can be either ebpf or ipfix. The IPFIX exporter will be possible to use regardless of that Agent type, and this feature does NOT change anything regarding the flow generation source.

      Ie when configuring the IPFIX export, the flow pipeline would either be:

      ebpf agent => flowlogs-pipeline (enricher) => ipfix export

      or:

      OVS / ipfix => flowlogs-pipeline (enricher) => ipfix export

      This feature request was initially made on github upstream: https://github.com/netobserv/network-observability-operator/issues/296

      ===

      CR example:

        exporters: 
           - type: IPFIX
             ipfix:
               targetHost: "ipfix-collector.ipfix.svc.cluster.local"
               targetPort: 4739
               transport: tcp or udp (optional - defaults to tcp)

              Unassigned Unassigned
              jtakvori Joel Takvorian
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: