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

Inject drop events in drop fields

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Proactive Architecture
    • False
    • None
    • False
    • NetObserv - Sprint 267, NetObserv - Sprint 268

      Since we introduced network events, we don't catch OVS_DROP_LAST_ACTION as drop anymore. 

      Dropped bytes / packets / cause and reason needs to be reintroduced in drop fields to keep metrics and graphs.

      This affects the user experience since we need to switch to network events to see the drop.

      https://github.com/netobserv/netobserv.github.io/pull/6#discussion_r1939152634

       

            [NETOBSERV-2092] Inject drop events in drop fields

            There are no comments yet on this issue.

              jpinsonn@redhat.com Julien Pinsonneau
              jpinsonn@redhat.com Julien Pinsonneau
              Mehul Modi Mehul Modi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: