Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incremental reporters #82

Closed
tsenart opened this issue Oct 16, 2014 · 3 comments
Closed

Incremental reporters #82

tsenart opened this issue Oct 16, 2014 · 3 comments

Comments

@tsenart
Copy link
Owner

tsenart commented Oct 16, 2014

With the previous work on making most of the data pipeline stream results as they come, it would be great to have a some new reporters which incrementally reflect new incoming data.

@mickey
Copy link
Contributor

mickey commented Feb 8, 2015

TLDR; https://asciinema.org/a/16198

Hey @tsenart here is a basic prototype for an incremental reporter that prints the latency of every requests to stdout.
In my video I pipe this to feedgnuplot to have a real time plot :D

Looking at only the first 4 characters of the reporter name might be a problem if adding more.

If you're interested I'd happily submit a pull request. Otherwise, what kind of reporter do you have in mind?

@tsenart
Copy link
Owner Author

tsenart commented Feb 9, 2015

Hey @mickey,

Thanks for your interest in this issue and for showing me feedgnuplot! I didn't know about it.
Since we now have a dump command which can be used in a pipeline with tools like feedgnuplot, I believe this issue can be closed. With that said, I don't think your change set is required to achieve what you want. Mind, though, that the latency is in nanoseconds so you'd have to convert it to milliseconds first. Anyways, here's an example (beware the possible output buffering done by awk which is platform dependent).

echo "GET http://:6060/" | vegeta attack -duration=60s -rate=200 | tee results.bin \
| vegeta dump -dumper="json" | jq '.latency' | awk '{print $1/1e6}' | feedgnuplot

@mickey
Copy link
Contributor

mickey commented Feb 9, 2015

Hey @tsenart thanks for your feedback!
I agree it doesn't make sense with the use of the dump command.
This is perfect, thanks!

@tsenart tsenart closed this as completed Feb 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants