Merge pull request #66927 from skrthomas/OSDOCS-7616

OSDOCS:7616: Adding Loki ResourceExhausted troubleshooting

Author: bscott-rh

modules/troubleshooting-network-observability-loki-resource-exhausted.adoc

@@ -0,0 +1,16 @@
+// Module included in the following assemblies:
+
+// * networking/network_observability/troubleshooting-network-observability.adoc
+
+:_content-type: PROCEDURE
+[id="network-observability-troubleshooting-loki-resource-exhausted_{context}"]
+= Troubleshooting Loki ResourceExhausted error
+Loki may return a `ResourceExhausted` error when network flow data sent by Network Observability exceeds the configured maximum message size. If you are using the Loki Operator, this maximum message size is configured to 100 MiB. 
+
+.Procedure
+. Navigate to *Operators* -> *Installed Operators*, viewing *All projects* from the *Project* drop-down menu.
+. In the *Provided APIs* list, select the Network Observability Operator.
+. Click the *Flow Collector* then the *YAML view* tab. 
+.. If you are using the Loki Operator, check that the `spec.loki.batchSize` value does not exceed 98 MiB.
+.. If you are using a Loki installation method that is different from the Red Hat Loki Operator, such as Grafana Loki, verify that the `grpc_server_max_recv_msg_size` link:https://grafana.com/docs/loki/latest/configure/#server[Grafana Loki server setting] is higher than the `FlowCollector` resource `spec.loki.batchSize` value. If it is not, you must either increase the `grpc_server_max_recv_msg_size` value, or decrease the `spec.loki.batchSize` value so that it is lower than the limit. 
+. Click *Save* if you edited the *FlowCollector*.

network_observability/troubleshooting-network-observability.adoc

@@ -18,6 +18,8 @@ include::modules/troubleshooting-network-observability-network-flow.adoc[levelof
 
 include::modules/troubleshooting-network-observability-controller-manager-pod-out-of-memory.adoc[leveloffset=+1]
 
+include::modules/troubleshooting-network-observability-loki-resource-exhausted.adoc[leveloffset=+1]
+
 == Resource troubleshooting
 
 include::modules/troubleshooting-network-observability-loki-tenant-rate-limit.adoc[leveloffset=+1]