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

Add charts for number of failures in the Web UI #952

Closed
liyanhui1228 opened this issue Jan 23, 2019 · 4 comments
Closed

Add charts for number of failures in the Web UI #952

liyanhui1228 opened this issue Jan 23, 2019 · 4 comments

Comments

@liyanhui1228
Copy link

Description of issue / feature request

Feature request:
Add charts for number of failures over
(1) time
(2) number of users

Expected behavior

Two more charts in the Web UI.

locust is a great tool for running load test and it will be nicer to have the charts about number of failures. I will spend some time working on this if this sounds useful.

@archived001
Copy link

Must have feature, the simple counter of percents failures not informative when trying to test in critical conditions. As example awesome charts you can see report for Yandex-tank performance tool https://overload.yandex.net/156114 (HTTP codes, response time distribution and other)

@heyman
Copy link
Member

heyman commented Oct 22, 2019

I'm +1 for (1). I think it would make sense to have a chart over the number of failures.

I don't think we need (2) (a graph with failures on Y axis and number of users on X axis). We already have a graph for number of users so one should be able to correlate them.

Must have feature, the simple counter of percents failures not informative when trying to test in critical conditions.

We've never had a huge focus on graphs (for a long time Locust didn't have graph at all). The focus has always been on providing the ability to generate load that simulates real user behaviour. If one want fancy graphs it's quite simple to make Locust report stats to Grafana or something similar.

@heyman
Copy link
Member

heyman commented Oct 22, 2019

@liyanhui1228 Sorry for the long wait. If you're still interested in working on this, I'd be happy to review the PR.

@cyberw
Copy link
Collaborator

cyberw commented Nov 18, 2019

solved in #1140

@cyberw cyberw closed this as completed Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants