Flower
Flower is an open-source web application for monitoring and managing Celery clusters. It provides real-time information about the status of Celery workers and tasks.
Features
- Real-time monitoring using Celery Events
View task progress and history
View task details (arguments, start time, runtime, and more)
- Remote Control
View worker status and statistics
Shutdown and restart worker instances
Control worker pool size and autoscale settings
View and modify the queues a worker instance consumes from
View currently running tasks
View scheduled tasks (ETA/countdown)
View reserved and revoked tasks
Apply time and rate limits
Revoke or terminate tasks
- Broker monitoring
View statistics for all Celery queues
HTTP Basic Auth, Google, Github, Gitlab and Okta OAuth
Prometheus integration
API
Installation
Installing flower with pip is simple
$ pip install flower
The development version can be installed from Github
$ pip install https://github.com/mher/flower/zipball/master#egg=flower
Usage
To run Flower, you need to provide the broker URL
$ celery --broker=amqp://guest:guest@localhost:5672// flower
Or use the configuration of celery application
$ celery -A tasks.app flower
By default, flower runs on port 5555, which can be modified with the port option
$ celery -A tasks.app flower --port=5001
You can also run Flower using the docker image
$ docker run -v $(pwd)/examples:/data -p 5555:5555 mher/flower celery --app=tasks.app flower
In this example, Flower is using the tasks.app defined in the examples/tasks.py file
API
The Flower API lets you manage the cluster over HTTP.
For example you can grow a worker’s pool by:
$ curl -X POST -d 'n=1' http://localhost:5555/api/worker/pool/grow/celery@$(hostname)
Or call a task by:
$ curl -X POST -d '{"args":[1,2]}' http://localhost:5555/api/task/async-apply/tasks.add
Or terminate a running task by:
$ curl -X POST -d 'terminate=True' http://localhost:5555/api/task/revoke/8a4da87b-e12b-4547-b89a-e92e4d1f8efd
For more info, see the API Reference
Documentation
Documentation is available at Read the Docs
License
Flower is licensed under BSD 3-Clause License. See the License file for the full license text.
Metadata
Release files for flower 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| flower-2.2.0.tar.gz | 1.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flower-2.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 1.5 MB
Release files / flower-2.2.0.tar.gz
| Download URL | flower-2.2.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4f4751942ff8b5069e6604a136e073b860971b7658859bdc61da1dc17a4bb32
|
|
BLAKE2b-256 checksum How to use checksums |
a6f93474dea8439722ff59804caba62532d08f147a2ffdf8cd8c8773e4b43faa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / flower-2.2.0-py2.py3-none-any.whl
| Download URL | flower-2.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 407.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
374cbdd92282576ffab66b0da3c3038a2ba1ec34b343b8197dca2e85ce4209f1
|
|
BLAKE2b-256 checksum How to use checksums |
b1b6650f730380002b78bcb488c0df96477dbdc57470731682587d6bc4951abf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for flower 2.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.