From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [RFC PATCH 0/7] Add script for real-time telemetry monitoring
Date: Fri, 12 Dec 2025 17:52:15 +0000 [thread overview]
Message-ID: <aTxWTww_gHjwQfBw@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251212143249.2fdbeaab@stephen-xps.local>
On Fri, Dec 12, 2025 at 02:32:49PM +0900, Stephen Hemminger wrote:
> On Wed, 10 Dec 2025 16:55:25 +0000
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> > TL;DR
> > ------
> >
> > For a quick demo, apply patces, run e.g. testpmd and then in a separate
> > terminal run:
> >
> > ./usertools/dpdk-telemetry-watcher.py -d1T eth.tx
> >
> > Output, updated once per second, will be traffic rate per port e.g.:
> >
> > Connected to application: "dpdk-testpmd"
> > Time /ethdev/stats,0.opackets /ethdev/stats,1.opackets Total
> > 16:29:12 5,213,119 5,214,304 10,427,423
> >
> >
<snip>
> >
> > usertools/dpdk-telemetry-watcher.py | 429 ++++++++++++++++++++++++++++
> > usertools/meson.build | 1 +
> > 2 files changed, 430 insertions(+)
> > create mode 100755 usertools/dpdk-telemetry-watcher.py
> >
> > --
> > 2.51.0
>
>
> The TUI patch was
> https://patchwork.dpdk.org/project/dpdk/patch/20220831115250.362189-2-conor.walsh@intel.com/
>
Took a look at that patch proposal, and here are some of the main
differences between the two scripts:
* the telemetry-tui is a full-screen app which is a lot prettier and
probably much more suitable for non-experts.
* the script I provided is FAR less user friendly and operates at a much
more "techie" level
* on the other hand, it's more flexible because of that:
- can be used to display any numeric stats - the tui is hard-coded to show
particular NIC stats - including e.g. cryptodev, or dmadev ones
- can show deltas and totals as desired
- can quit after a certain fixed amount of time
* my script is probably more limited in terms of what can be displayed,
since it assumes that you want one-line of output per update. TUI
displays lots of (fixed)stats simultaneously
* TUI as proposed has a few glitches - got a divide by zero error when run
against a testpmd instance that didn't have traffic running, so all stats
were zero. (That's an easy fix though)
* The new script I propose has one major feature that I would look to add
to the TUI if we merged that - the reconnection support. I find it very
handy to run the watcher script and leave it running while I start and
stop whatever app(s) I'm using.
* My script has no additional dependencies beyond stock python, while the
TUI requires one additional dependency "rich" to manage the TUI. It also
can use a second dependency "plotext" (not Ubuntu packaged) to display
charts if so desired.
Just my quick assessment of the two from a quick try of the TUI one.
/Bruce
next prev parent reply other threads:[~2025-12-12 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 16:55 [RFC PATCH 0/7] Add script for real-time telemetry monitoring Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 1/7] usertools: add new script to monitor telemetry on terminal Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 2/7] usertools/telemetry-watcher: add displaying stats Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 3/7] usertools/telemetry-watcher: add delta and timeout opts Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 4/7] usertools/telemetry-watcher: add total and one-line opts Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 5/7] usertools/telemetry-watcher: add thousands separator Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 6/7] usertools/telemetry-watcher: add eth name shortcuts Bruce Richardson
2025-12-10 16:55 ` [RFC PATCH 7/7] usertools/telemetry-watcher: support reconnection Bruce Richardson
2025-12-11 1:09 ` [RFC PATCH 0/7] Add script for real-time telemetry monitoring Stephen Hemminger
2025-12-11 9:10 ` Bruce Richardson
2025-12-12 5:32 ` Stephen Hemminger
2025-12-12 17:52 ` Bruce Richardson [this message]
2025-12-12 23:23 ` Stephen Hemminger
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=aTxWTww_gHjwQfBw@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).