From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, shemminger@vyatta.com,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH iproute2] ss: make socket statistic parseable
Date: Sun, 20 Oct 2013 15:24:27 +0200 [thread overview]
Message-ID: <20131020132427.GA4514@virgo.local> (raw)
In-Reply-To: <1382219776.3284.49.camel@edumazet-glaptop.roam.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
* Eric Dumazet | 2013-10-19 14:56:16 [-0700]:
>Seems fine to me, maybe we want to support json for better parsing
>capabilities ?
Currently the parsing is straight forward with Python: split for
whitespaces and subsequent split for colon to get a key/value list. Supporting
an additional format may be overhead - not sure?! But yeah, JSON formated
output is nice too. The current format has the advantage that it is human
readable and "good" machine parseable. Except the first line:
tcp ESTAB 0 0 192.168.1.29:58951 208.68.163.218:xmpp-cli
The line has a strict order, so it is not that hard to write a correct parser.
Btw: for people not following google plus circus: I wrote an parser for ss(8)
for plotting TCP stack variables:
http://research.protocollabs.com/captcp/doc-socket-statistic-module.html
Cheers, Hagen
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-10-20 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 17:54 [PATCH iproute2] ss: make socket statistic parseable Hagen Paul Pfeifer
2013-10-19 21:56 ` Eric Dumazet
2013-10-20 13:24 ` Hagen Paul Pfeifer [this message]
2013-10-20 13:44 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131020132427.GA4514@virgo.local \
--to=hagen@jauu.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).