With v9 and IPFIX, there are literally dozens of Flow templates that can be defined by the Hardware vendors. Some of these templates should be ignored by Flowview as they will end up inserting invalid data. For example, Mikrotik supports Templates: 256-259. However, only Templates: 256 (ipV4 information) and 259 (ipV6 information) are useful for Flowview. The others will end up polluting the data.
So, cacti should inspect the Templates and only process those that cover the fields initially supported by V5 until such time as Flowview Developers desire to support various V9 and IPFIX templates that provide other information.
Describe the bug
With v9 and IPFIX, there are literally dozens of Flow templates that can be defined by the Hardware vendors. Some of these templates should be ignored by Flowview as they will end up inserting invalid data. For example, Mikrotik supports Templates: 256-259. However, only Templates: 256 (ipV4 information) and 259 (ipV6 information) are useful for Flowview. The others will end up polluting the data.
So, cacti should inspect the Templates and only process those that cover the fields initially supported by V5 until such time as Flowview Developers desire to support various V9 and IPFIX templates that provide other information.
Expected behavior
Only import supported Template