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

Add a way to identify agent in flows

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • netobserv-1.2
    • None
    • None
    • None
    • NetObserv - Sprint 229, NetObserv - Sprint 230, NetObserv - Sprint 231

    Description

      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.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. NETOBSERV-696 Reporter node behaves the opposite of what it says

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. NETOBSERV-697 By default, return traffic from external requests are not in flow table.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              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

              Dates

                Created:
                Updated:
                Resolved: