How blueswen/flask-monitoring works
This repository demonstrates Flask request monitoring: requests enter the Flask app, middleware emits tagged StatsD metrics, statsd_exporter exposes them for Prometheus scraping, and Grafana queries Prometheus to display the predefined RED dashboard. The README documents the service and provisioning relationships; source excerpts show app initialization and metric instrumentation. The external services’ implementations are not in the tree.
Main entry points: app.py Flask routes · utils.py StatsD middleware · prometheus.yml Scrape configuration · datasource.yml Datasource configuration
Components 11
Flask Instrumentation
- Flask routes
flask_app/app.py - StatsD middleware
flask_app/utils.py - Datadog StatsD client
Metrics Collection
- statsd_exporter
- Scrape configuration
etc/prometheus/prometheus.yml - Prometheus
Queries and Dashboards
- Datasource configuration
etc/grafana/datasource.yml - Dashboard provisioning
etc/dashboards.yaml - Monitoring dashboard
etc/dashboards/flask-monitoring.json - Grafana
Other components
- Requesting client
Connections 10
- Requesting client → Flask routes: sends requests
readme.md - Flask routes → StatsD middleware: installs
flask_app/app.py - StatsD middleware → Datadog StatsD client: emits metrics
flask_app/utils.py - Datadog StatsD client → statsd_exporter: sends UDP metrics
readme.md - Prometheus → statsd_exporter: scrapes metrics
readme.md - Scrape configuration → Prometheus: configures scrape
readme.md - Datasource configuration → Grafana: configures datasource
readme.md - Dashboard provisioning → Grafana: provisions dashboard
readme.md - Grafana → Prometheus: queries data
readme.md - Grafana → Monitoring dashboard: displays
readme.md