-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
None
-
None
-
None
With day-0 install, it is more likely that users start using netobserv without realizing how it is configured.
So it becomes even more important that we communicate, through the UI, the most impacting configs so they understand what they (don't) see. Users often ask "why don't I see any flow when doing X", and often times the answer is "because you have sampling".
Suggestion (others are welcome) : when sampling > 0, add a dismissable banner telling that not all flows are captured because of sampling. Banner being dismissed is stored in local storage.
We could also include the information about ebpf or FLP filters being configured, but not necessarily as visible as that, since it's not a default config, as cluster admin have explicitly configured it hence it shouldn't come up as a surprise.