Observed since 20 Oct, 17:05 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
An Alliance Auth app for monitoring celery tasks.
An Alliance Auth app for monitoring celery tasks.
Task Monitor enables administrators to monitor celery tasks running on their system.




Task Monitor is a plugin for Alliance Auth. If you don't have Alliance Auth running already, please install it first before proceeding. (see the official AA installation guide for details)
Make sure you are in the virtual environment (venv) of your Alliance Auth installation. Then install the newest release from PyPI:
pip install aa-taskmonitor
Configure your Auth settings (local.py) as follows:
'taskmonitor' to INSTALLED_APPSRun migrations & copy static files
python manage.py migrate
python manage.py collectstatic --noinput
Restart your supervisor services for Auth.
You can manage your logs and queue also directly via a command line utility.
The basic syntax for using the utility is:
python manage.py taskmonitorctl {command} {target}
For example you can inspect your logs with:
python manage.py taskmonitorctl inspect logs
Or for example you can purge your task queue with:
python manage.py taskmonitorctl purge queue
To get an overview of available commands run:
python manage.py taskmonitorctl --help
To get an overview of available targets for a command run:
python manage.py taskmonitorctl inspect --help
Here is a list of available settings for this app. They can be configured by adding them to your AA settings file (local.py).
Note that all settings are optional and the app will use the documented default settings if they are not used.
| Name | Description | Default |
|---|---|---|
TASKMONITOR_APP_NAME_MAPPING_CONFIG | Ability to map tasks to the same app name. Map must be a dictionary with string keys and list of strings as value. All app names in the list will be replaced by it's key. | {} |
TASKMONITOR_DATA_MAX_AGE | Max age of logged tasks in hours. Older logs be deleted automatically. | 24 |
TASKMONITOR_DELETE_STALE_BATCH_SIZE | Size of task logs deleted together in one batch. | 5000 |
TASKMONITOR_ENABLED | Global switch to enable/disable task monitor. | True |
TASKMONITOR_HOUSEKEEPING_FREQUENCY | Frequency of house keeping runs in minutes. | 30 |
TASKMONITOR_QUEUED_TASKS_ADMIN_LIMIT | The admin page will stop showing the list of queued tasks above this limit to protect against crashing caused by too high memory consumption. | 100000 |
TASKMONITOR_QUEUED_TASKS_CACHE_TIMEOUT | Timeout for caching queued tasks in seconds. 0 will deactivate the cache. | 10 |
TASKMONITOR_REPORTS_MAX_AGE | Max age of cached reports in minutes. | 60 |
TASKMONITOR_REPORTS_MAX_TOP | Max items to show in the top reports. e.g. 10 will shop the top ten items. | 20 |
TASKMONITOR_TRUNCATE_NESTED_DATA | Whether deeply nested task params and results are truncated. | True |
Yes, there is a setting, which you can increase according to your needs. However, please keep in mind that your storage needs will increase accordingly. The current approx. usage is 0.5 KB per entry, so e.g. you need approx. 500 MB to store 1.000.000 task logs. Note that you can use the command line utility to find out how much space your logs are currently using.
Celery Analytics seams to be designed mainly as data source for reports on Grafana. It apparently works great if you want to integrate analysis about your task executions into a Grafana dashboards. But it's usability without Grafana is limited.
Task Monitor on the other hand aims to be fully functional standalone by providing reports and many useful features for analyzing your task logs directly on the admin site. It also provides a more complete picture, since Celery Analytics ignores retried tasks.
Flower offers more detailed and technical information about task runs and might therefore be more most for developers. However, it not designed to store a larger number of task logs (default is only 10K) and is appears therefore to be less suited for Alliance Auth, where you typically have 100K+ tasks per day.
Task Monitor has data truncating enabled by default. It is applied when storing args, kwargs and results in task logs. This helps to reduce the storage consumptions and also makes the task log better readable. But it can be turned off.
Task args are truncated by clearing all nested containers.
Example: [1, [2, 3], 4] becomes [1, [], 4]
Task kwargs are truncated by clearing all nested containers in values.
Example: {"a": [1, 2], "b": 3} becomes {"a": [], "b": 3}
Finally, task results are truncated like args and kwargs depending on their type. In addition lists of empty containers are compressed.
Example: [ [], [], [] ] becomes []
Download counts and popularity will appear here as the collector receives them.
| Version | Published | Direct dependencies | Open version |
|---|---|---|---|
| 1.1.1 | 30 Jun 2026 | 5 |
This describes our collected data; it is not a security assessment.
Shared repository data · GitHub
Observed since 20 Oct, 17:05 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package:71cc844822dd3f29f91b6520dc641af174bb547dc49f62a89180752e50f63d43