-
Bug
-
Resolution: Done
-
Normal
-
netobserv-1.8
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
NetObserv - Sprint 268
-
None
-
None
-
Previously it was not obvious to figure out there was an issue when referencing a LokiStack from the FlowCollector resource, such as in case of typo. Now, the FlowCollector status clearly states that the referenced LokiStack is not found in that case.
1. If using a LokiStack, it defaults to the name "loki". This is not obvious. Even when you select LokiStack as the Loki mode, you still need to open up the "Loki stack" (sic) section to see what name it has chosen (see LokiStack-config screenshot).
Suggestion: Automatically open up the LokiStack section. Also fix the spelling "Loki stack" to "LokiStack".
2. Even with the incorrect LokiStack name, the Status column in the FlowCollectors page gives no indication of that (see FlowCollectors-status screenshot). It says "Conditions: MonitoringReady, NetworkPolicyReady".
Suggestion: Indicate that something is wrong, ideally saying the LokiStack could not be found.
3. If you click the "cluster" link, the Conditions section does indicate something is wrong (see cluster screenshot). There are errors on:
- configmaps "loki-gateway-ca-bundle" not found
- 2 ready components, 3 with failure, 0 pending
It still isn't clear what is wrong.
Suggestion: Indicate that LokiStock could not be found
