You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 7, 2023. It is now read-only.
kube-netc exposes quite a lot of data in its current state. We were thinking about implementing a method to narrow down the metrics exposed to a given namespace. This can be done now at the end by querying the metrics for our source and destination namespace labels, but they still bog down Prometheus.
The proposed feature would halt the tracking of networking stats if it found that they are coming from an ip that is known to be outside a certain namespace.
The text was updated successfully, but these errors were encountered:
kube-netc exposes quite a lot of data in its current state. We were thinking about implementing a method to narrow down the metrics exposed to a given namespace. This can be done now at the end by querying the metrics for our source and destination namespace labels, but they still bog down Prometheus.
The proposed feature would halt the tracking of networking stats if it found that they are coming from an ip that is known to be outside a certain namespace.
The text was updated successfully, but these errors were encountered: