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
Hello!
If you save it to a file in the JSON format, then a lot of traffic is generated and it takes up a lot of space (even with compression). It would be very nice to be able to save to a file in CSV format
Thank you!
The text was updated successfully, but these errors were encountered:
to be honest, I don't think any text file format is suitable for storing big data.
The disadvantage of CSV formatting is that you need to directly specify the fields that should appear in each column. In other words, you need to know exactly what is in the data of the exporter and what you want to store. In contrast, the good thing about JSON is that it is a very flexible format that allows you to easily convert very flexible IPFIX records.
We currently have no plans to add support for formatting to a CSV file in the near future.
What you can currently do is store the data in the Nffile format and then use a tool like Nfdump to read the data as CSV. There's a problem that Nfdump doesn't fully support all that IPFIX has to offer, but if you don't use any special fields it might be a suitable solution for you.
There's also the FDS format designed to be even more efficient, but the equivalent Fdsdump tool is still in development. Once that's done, that would probably be the better choice.
Hello!
If you save it to a file in the JSON format, then a lot of traffic is generated and it takes up a lot of space (even with compression). It would be very nice to be able to save to a file in CSV format
Thank you!
The text was updated successfully, but these errors were encountered: