-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing NetFlow Option packets #15075
Comments
For My netflowV9 and IPFIX I am sending snmp option packets with interface snmp mib to long/short name mappings. Looks like telegarf is ignoring these option packets. See IOS XE configuration below along with exporter templates details for the Option options interface-table. IOS XE exporter configurations:
Should this work out of the box? or is this a new feature request? |
Telegraf logs |
@SirBreadc currently option data-flow-sets are not processed by the plugin. Could you please provide some samples of the data using the |
log_telegarf_snmp_options_table.zip ` Exporter Format: NetFlow Version 9 | Field | Type | Offset | Size || v9-scope system | 1 | 0 | 4 | |
@SirBreadc I've added Netflow v9 options support in PR #15180, available as soon as CI finished the builds. Please give it a try and let me know if this what you expect. The options are reported as Just for clarification, the "missing template" warnings are an inherent problem of the netflow protocol. The warning will disappear once the device will resend the templates. This cannot be triggered by Telegraf and without the templates the data cannot be interpreted... This mostly happens if you start/restart after the device established a connection to Telegraf... |
@srebhan Thanks that works well, can this also be added for IPFIX too? as I am only seeing the netflow_option packet for our V9 devices. Will get you a dump for one of those devices if that's needed |
Yeah I would need another dump from those devices and another feature-request if possible... |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.30, Centos,CentOS Linux 7
Docker
No response
Steps to reproduce
Expected behavior
Option packets are also writen to output
Actual behavior
Option packets are not written to outputs
Additional info
No response
The text was updated successfully, but these errors were encountered: