Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-759

Add a way to identify agent in flows

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • netobserv-1.2
    • None
    • None
    • None
    • BU Product Work
    • False
    • None
    • False
    • OCPSTRAT-458 - OpenShift Network Observability Operator enhancements
    • NetObserv - Sprint 229, NetObserv - Sprint 230, NetObserv - Sprint 231

      When troubleshooting, it is sometimes useful to understand which agent reported a given flow, especially when trying to reason about the duplicates & ingress/egress.

      We should add such an identifying field, e.g. AgentIP or ObservationPoint or ReporterIP ...

      Also the FlowLogs-Pipeline must be able to read this information and add the proper field in the JSON that is written to loki.

              mmaciasl@redhat.com Mario Macias (Inactive)
              jtakvori Joel Takvorian
              Mehul Modi Mehul Modi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: