-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.15
-
Important
-
None
-
1
-
OSDOCS Sprint 255, OSDOCS Sprint 256
-
2
-
False
-
Description of problem:
As it's observed in the article https://access.redhat.com/solutions/7050424, an errata was released to be able to set a different timeout when querying flows from the OCP Console. Before the erratas, the value was 30s. After releasing the ERRATAs, the default value for the netobserv-plugin continues to be 30s and for modifying it, it's needed to change the `flowcollector.spec.loki.readTimeout`, but this is not documented when "Installing" [1] network observability or when "Configuring" [2]
Version-Release number of selected component (if applicable):
Network observability 1.5
Expected results:
I'd expect to see documented the option `flowcollector.spec.loki.readTimeout` to know how to change the default timeout of 30s when using the OCP Console when querying the network traffic
[1]https://docs.openshift.com/container-platform/4.15/observability/network_observability/installing-operators.html
[2]https://docs.openshift.com/container-platform/4.15/observability/network_observability/configuring-operator.html
- is related to
-
NETOBSERV-1443 Console plugin loki timeout should be configurable
- Closed
- links to
(4 links to)