-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
5
-
None
-
None
-
None
As a follow-up on NETOBSERV-122, we want to expose the status when goflow is technically ready (it is listening & getting flows) however it isn't yet able to interpret them because it hasn't received the related template definitions.
This information is currently provided by goflow in a metric: https://github.com/netsampler/goflow2/blob/20e8e567090cd0c736c925dd86fb8edc33bc740c/utils/netflow.go#L110-L116
So this metric should be read and transformed into a health status.
Note that we don't want, at this point, to make it mandatory to deploy prometheus as part of our infra. It means the metrics would have to be read from the goflow service itself (in prometheus format), and not from prometheus.
If for some reason it turns out not to be a good option, we could also investigate adding such health information directly in goflow code (instead of our goflow-kube)
- relates to
-
NETOBSERV-122 Goflow: expose status
-
- Closed
-
- links to