Metrics generated by the flowlogs-pipeline
are configurable in the spec.processor.metrics.includeList
of the FlowCollector
custom resource to add or remove metrics.
You can also create alerts by using the includeList
metrics in Prometheus rules, as shown in the example "Creating alerts".
When looking for these metrics in Prometheus, such as in the Console through Observe → Metrics, or when defining alerts, all the metrics names are prefixed with `netobserv_. For example, `netobserv_namespace_flows_total. Available metrics names are as follows.
includeList metrics names
Names followed by an asterisk *
are enabled by default.
-
namespace_egress_bytes_total
-
namespace_egress_packets_total
-
namespace_ingress_bytes_total
-
namespace_ingress_packets_total
-
namespace_flows_total
*
-
node_egress_bytes_total
-
node_egress_packets_total
-
node_ingress_bytes_total
*
-
node_ingress_packets_total
-
node_flows_total
-
workload_egress_bytes_total
-
workload_egress_packets_total
-
workload_ingress_bytes_total
*
-
workload_ingress_packets_total
-
workload_flows_total
PacketDrop metrics names
When the PacketDrop
feature is enabled in spec.agent.ebpf.features
(with privileged
mode), the following additional metrics are available:
-
namespace_drop_bytes_total
-
namespace_drop_packets_total
*
-
node_drop_bytes_total
-
node_drop_packets_total
-
workload_drop_bytes_total
-
workload_drop_packets_total
DNS metrics names
When the DNSTracking
feature is enabled in spec.agent.ebpf.features
, the following additional metrics are available:
FlowRTT metrics names
When the FlowRTT
feature is enabled in spec.agent.ebpf.features
, the following additional metrics are available:
-
namespace_rtt_seconds
*
-
node_rtt_seconds
-
workload_rtt_seconds