Wireshark-bugs: [Wireshark-bugs] [Bug 10759] New: Tshark -z io, stat options export to csv forma

Date: Fri, 05 Dec 2014 23:35:23 +0000
Bug ID 10759
Summary Tshark -z io,stat options export to csv format
Product Wireshark
Version 1.12.2
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component TShark
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 1.12.0 (v1.12.0-0-g4fab41a from master-1.12)

Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 31 2014),
with
AirPcap.

Running on 64-bit Windows 8.1, build 9600, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
        Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, with 8078MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I would like to request a change in the output of -z io,stat of tshark, so that
it provides measurements as they've been requested into a simple .csv format.
This would make automated/scripted use of the command much easier than the
ASCII text output that it presents now.

One difficulty with the current format is that, while all stats are held to a
single line of text, it is not a fixed line number of the output (ie: adding
another counter means that the output will produce one more line before the
line containing all the measurements).

Another difficulty is that frames and bytes in some measurement types are
presented and delimited separately whereas other measurement types give only
one return column (eg: AVG() or MIN() functions), requiring a script to know
how many column returns result from what types of measurements, reading the
header information in the output to do all the correlation.

A simple .csv output where all returns are a single delimited value would, I
believe, make many people's lives easier here.


You are receiving this mail because:
  • You are watching all bug changes.