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

It is not possible to filter on "n/a" latency

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Previously in the console plugin, it wasn't always possible to filter for unset fields, such as unset DNS latency.
      With this patch, filtering on unset fields is now possible.
      Show
      Previously in the console plugin, it wasn't always possible to filter for unset fields, such as unset DNS latency. With this patch, filtering on unset fields is now possible.
    • NetObserv - Sprint 259

      Description of problem:

      When using network observability to monitor dropped DNS flows, it was clear that these drops would manifest as n/a latency. However, the filtering field in the network observability console UI could only accept an integer value.

      Steps to Reproduce:

      1. Attempt to filter network traffic flows to latency n/a

      Actual results:

      Regex validation blocks the input

      Expected results:

      User should be able to filter on n/a

       

      --- 

       

      Users will now be able to filter on strice value "" resolving as n/a in the display.

      This search will match both empty strings or missing field.

              jpinsonn@redhat.com Julien Pinsonneau
              jupierce Justin Pierce
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: