Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Run locust as a job but still have access to the API.

See original GitHub issue

Is your feature request related to a problem? Please describe.

I want to be able to run locust as a job i.e. locust -c 100 -r 10 --run-time 30m and still have access to the stats API and custom endpoints. Right now it forces me to run it with --no-web which removes API access.

Describe the solution you’d like

Allow them to run together or partial versions of them.

Describe alternatives you’ve considered

Starting up a separate Flask server

Additional context

Issue Analytics

State:
Created 3 years ago
Reactions:4
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

heymancommented, Apr 21, 2020

Maybe we could have a new option, like --swarm-delay/-d, which could double as a way to specify automatic start in web-mode, and to provide a delay to start the test in both web and headless mode.

I’m not very fond of adding an extra command line option for this. It doesn’t seem like a common enough use-case.

Here’s documentation on how to start the WebUI using code in 1.0: https://docs.locust.io/en/latest/use-as-lib.html

0reactions

cyberwcommented, May 22, 2020

I think @heyman s last comment is a good solution for this.