From: Rich Brown <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] Charting ping_hosts (#181)
Date: Fri, 13 Sep 2019 18:45:32 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/181/531435371@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/181@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
I do see your point. I'm casting about to find a good way to show this, especially when pulling results from separate data files, where the file names won't be a particularly good way to indicate a difference. Alternatives:
* The legend at the bottom "Local/Remote: localhost/flent-fremont.bufferbloat.net - Time: 2019... " could include "Pinging 1.2.3.4"
* Or perhaps "Local/Remote/Pinging: localhost/flent-fremont.bufferbloat.net/1.2.3.4 - Time: 2019... "
* Or in the case that Flent was combining separate data files, (actually, anytime the ping host is different from the -H host) perhaps the plot legend (on the right of the chart) could include the IP address of the alternate ping host - that is, "Ping to 1.2.3.4 (ms)" instead of "Ping (ms)"
PS I'm not meaning to be glib, or trying to ignore other important situations. I expect this particular use case to be very common, and so want to make sure it looks great in the test results and charts. Thanks.
*I'm mostly adding the image to prompt my memory of how the chart looks, not for new information*
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/181#issuecomment-531435371
[-- Attachment #1.2: Type: text/html, Size: 2972 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
prev parent reply other threads:[~2019-09-14 1:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 15:39 Rich Brown
2019-09-11 11:54 ` Rich Brown
2019-09-11 12:05 ` Rich Brown
2019-09-11 12:07 ` Toke Høiland-Jørgensen
2019-09-11 12:17 ` Rich Brown
2019-09-11 15:15 ` Toke Høiland-Jørgensen
2019-09-11 16:12 ` Rich Brown
2019-09-11 17:27 ` Toke Høiland-Jørgensen
2019-09-11 18:13 ` Rich Brown
2019-09-13 16:27 ` Toke Høiland-Jørgensen
2019-09-13 17:13 ` Rich Brown
2019-09-13 22:01 ` Toke Høiland-Jørgensen
2019-09-14 1:45 ` Rich Brown [this message]
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
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issues/181/531435371@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPZYRGJUEMXI6ETUCMN3RGDMZEVBNHHB2T4L5Y@reply.github.com \
--cc=subscribed@noreply.github.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