How spscommerce/fulfillment-celery-exporter works
celery-exporter consumes Celery’s brokered events, updates Prometheus task and worker metrics, and serves them over HTTP for scraping; it also provides a broker health endpoint. Its Celery-mixin supplies Grafana dashboards and Prometheus alerts. Runtime relationships are grounded in the sampled source; the mixin’s role and dashboard/alert capabilities are documented in the README, but its generation internals were not sampled.
Main entry points: exporter.py Event exporter · cli.py CLI options · http_server.py HTTP endpoints · dashboards.libsonnet Dashboard mixin
Components 13
Exporter runtime
- CLI options
src/cli.py - Metric help
src/help.py - Event exporter
src/exporter.py - HTTP endpoints
src/http_server.py
Monitoring assets
- Dashboard definitions
celery-mixin/dashboards/dashboards.libsonnet - Dashboard mixin
celery-mixin/dashboards/dashboards.libsonnet - Alert rules
celery-mixin/prometheus-alerts.yaml - Alert mixin
celery-mixin/alerts/alerts.libsonnet
External systems
- Celery workers
- Message broker
- Prometheus
- Grafana
Other components
- Operator
Connections 13
- Operator → CLI options: configures
README.md - CLI options → Event exporter: starts
src/cli.py - CLI options → Metric help: loads help
src/cli.py - Celery workers → Message broker: send events
README.md - Message broker → Event exporter: supplies events
README.md - Event exporter → Message broker: connects
src/exporter.py - Event exporter → HTTP endpoints: starts server
src/exporter.py - Prometheus → HTTP endpoints: scrapes metrics
README.md - HTTP endpoints → Message broker: checks health
src/http_server.py - Dashboard definitions → Dashboard mixin: defines dashboards
- Dashboard mixin → Grafana: provides dashboards
README.md - Alert rules → Alert mixin: defines alerts
- Alert mixin → Prometheus: provides alerts
README.md