summaryrefslogtreecommitdiff
path: root/data/templates/sflow
diff options
context:
space:
mode:
authorViacheslav Hletenko <v.gletenko@vyos.io>2023-03-17 12:38:27 +0000
committerViacheslav Hletenko <v.gletenko@vyos.io>2023-03-17 12:43:13 +0000
commit57c06dcd78f9b711c4fb46e6657b0a496059a685 (patch)
tree0a37d9f887ac862cbd6f8122b88e8f4eafa1f582 /data/templates/sflow
parentda42b37983e75dc4587160036be9eb71df4e4989 (diff)
downloadvyos-1x-57c06dcd78f9b711c4fb46e6657b0a496059a685.tar.gz
vyos-1x-57c06dcd78f9b711c4fb46e6657b0a496059a685.zip
T5086: Add sFlow drop-monitor-limit option
hsflowd will export the headers of dropped packets (along with the name of the function in the Linux kernel where that skb was dropped) as part of the standard sFlow feed. This measurement complements the sFlow packet sampling and counter-telemetry well because it provides visibility into the traffic that is not flowing. Very helpful for troubleshooting. The limit (a rate limit max of N drops per second sent out in the sFlow datagrams) is the parameter you would set in the CLI. set system sflow drop-monitor-limit 50
Diffstat (limited to 'data/templates/sflow')
-rw-r--r--data/templates/sflow/hsflowd.conf.j23
1 files changed, 3 insertions, 0 deletions
diff --git a/data/templates/sflow/hsflowd.conf.j2 b/data/templates/sflow/hsflowd.conf.j2
index 7ce6554d7..94f5939be 100644
--- a/data/templates/sflow/hsflowd.conf.j2
+++ b/data/templates/sflow/hsflowd.conf.j2
@@ -25,4 +25,7 @@ sflow {
pcap { dev={{ iface }} }
{% endfor %}
{% endif %}
+{% if drop_monitor_limit is vyos_defined %}
+ dropmon { limit={{ drop_monitor_limit }} start=on sw=on hw=off }
+{% endif %}
}