mher/flower

Real-time monitor and web admin for Celery distributed task queue

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 9th, 2026
Created on July 8th, 2012
Open Issues & Pull Requests: 58 (+0)
GitHub issues: Enabled
Number of forks: 1,155
Total Stargazers: 7,243 (+0)
Total Subscribers: 135 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 1
Closed in 7 days: 85
Avg open age: 749 days
Stale 30+ days: 10
Stale 90+ days: 10

Recent activity

Opened in 7 days: 1
Closed in 7 days: 85
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (69)
  • enhancement (32)
  • tasks (7)
  • api (3)
  • dashboard (1)
  • docker (1)
  • docs (1)
  • monitor (1)

Detailed Description

Flower is a web-based monitoring and administration tool for Celery distributed task queues.

Flower solves the problem of gaining visibility and control over Celery clusters by providing real-time monitoring through Celery Events. It displays task progress, history, and detailed task information including arguments, start time, and runtime. The tool enables remote control of workers, allowing operators to shutdown or restart instances, adjust pool sizes, modify queue assignments, and manage task execution through revocation or termination. It also monitors broker statistics across all queues and integrates with Prometheus for metrics collection.

Flower suits teams running Celery-based distributed task systems who need operational visibility and the ability to manage workers and tasks from a central interface. It works with brokers including RabbitMQ and Redis. The tool offers multiple authentication options including HTTP Basic Auth and OAuth providers like Google, Github, Gitlab, and Okta. Beyond the web interface, Flower exposes a REST API that enables programmatic cluster management, such as restarting worker pools or revoking tasks via HTTP requests.

The project maintains active development with regular updates to its codebase. Build workflows are consistently executed to validate changes. The tool is distributed through multiple channels including pip and Docker, indicating sustained attention to accessibility and deployment patterns. Documentation is maintained at a dedicated site, suggesting ongoing effort to keep guidance current alongside code evolution.