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

Console plugin loki timeout should be configurable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • netobserv-1.5
    • netobserv-1.4
    • Console Plugin
    • None
    • False
    • None
    • False
    • Hide
      Previously, console plugin read timeout was forced to 30s.
      Since FlowCollector v1beta2 API update, you can configure `readTimeout` in `loki` section to update this value accordingly with loki operator `queryTimeout` limit.
      Show
      Previously, console plugin read timeout was forced to 30s. Since FlowCollector v1beta2 API update, you can configure `readTimeout` in `loki` section to update this value accordingly with loki operator `queryTimeout` limit.
    • NetObserv - Sprint 246, NetObserv - Sprint 247, NetObserv - Sprint 248

      Description of problem:

      Loki operator timeout has been increased but console plugin read timeout is hardcoded to 30s

https://access.redhat.com/solutions/6998442
https://github.com/netobserv/network-observability-operator/blob/main/controllers/consoleplugin/consoleplugin_objects.go#L303-L344

      Steps to Reproduce:

      1.Install Loki 5.6.14
2.Run a long query (remove all filters + increase time range > 6h)

      Actual results:

      You may get timeout

      Expected results:

      Timeout should be configurable or match loki operator one

       

      Related slack:

      https://redhat-internal.slack.com/archives/C01DMAD88JF/p1703077751653949 

              jpinsonn@redhat.com Julien Pinsonneau
              rhn-support-ocasalsa Oscar Casal Sanchez
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: