Django middlewares to monitor your application with Prometheus.io.
Project description
django-prometheus
Export Django monitoring metrics for Prometheus.io
Features
This library provides Prometheus metrics for Django related operations:
- Requests & Responses
- Database access done via Django ORM
- Cache access done via Django Cache framework
Usage
Requirements
- Django >= 2.2
Installation
Install with:
pip install django-prometheus
Or, if you're using a development version cloned from this repository:
python path-to-where-you-cloned-django-prometheus/setup.py install
This will install prometheus_client as a dependency.
Quickstart
In your settings.py:
INSTALLED_APPS = [
...
'django_prometheus',
...
]
MIDDLEWARE = [
'django_prometheus.middleware.PrometheusBeforeMiddleware',
# All your other middlewares go here, including the default
# middlewares like SessionMiddleware, CommonMiddleware,
# CsrfViewmiddleware, SecurityMiddleware, etc.
'django_prometheus.middleware.PrometheusAfterMiddleware',
]
In your urls.py:
urlpatterns = [
...
url('', include('django_prometheus.urls')),
]
Configuration
Prometheus uses Histogram based grouping for monitoring latencies. The default buckets are here: https://github.com/prometheus/client_python/blob/master/prometheus_client/core.py
You can define custom buckets for latency, adding more buckets decreases performance but increases accuracy: https://prometheus.io/docs/practices/histograms/
PROMETHEUS_LATENCY_BUCKETS = (.1, .2, .5, .6, .8, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.5, 9.0, 12.0, 15.0, 20.0, 30.0, float("inf"))
Monitoring your databases
SQLite, MySQL, and PostgreSQL databases can be monitored. Just
replace the ENGINE property of your database, replacing
django.db.backends with django_prometheus.db.backends.
DATABASES = {
'default': {
'ENGINE': 'django_prometheus.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
},
}
Monitoring your caches
Filebased, memcached, redis caches can be monitored. Just replace
the cache backend to use the one provided by django_prometheus
django.core.cache.backends with django_prometheus.cache.backends.
CACHES = {
'default': {
'BACKEND': 'django_prometheus.cache.backends.filebased.FileBasedCache',
'LOCATION': '/var/tmp/django_cache',
}
}
Monitoring your models
You may want to monitor the creation/deletion/update rate for your model. This can be done by adding a mixin to them. This is safe to do on existing models (it does not require a migration).
If your model is:
class Dog(models.Model):
name = models.CharField(max_length=100, unique=True)
breed = models.CharField(max_length=100, blank=True, null=True)
age = models.PositiveIntegerField(blank=True, null=True)
Just add the ExportModelOperationsMixin as such:
from django_prometheus.models import ExportModelOperationsMixin
class Dog(ExportModelOperationsMixin('dog'), models.Model):
name = models.CharField(max_length=100, unique=True)
breed = models.CharField(max_length=100, blank=True, null=True)
age = models.PositiveIntegerField(blank=True, null=True)
This will export 3 metrics, django_model_inserts_total{model="dog"},
django_model_updates_total{model="dog"} and
django_model_deletes_total{model="dog"}.
Note that the exported metrics are counters of creations, modifications and deletions done in the current process. They are not gauges of the number of objects in the model.
Starting with Django 1.7, migrations are also monitored. Two gauges
are exported, django_migrations_applied_by_connection and
django_migrations_unapplied_by_connection. You may want to alert if
there are unapplied migrations.
If you want to disable the Django migration metrics, set the
PROMETHEUS_EXPORT_MIGRATIONS setting to False.
Monitoring and aggregating the metrics
Prometheus is quite easy to set up. An example prometheus.conf to
scrape 127.0.0.1:8001 can be found in examples/prometheus.
Here's an example of a PromDash displaying some of the metrics collected by django-prometheus:
Adding your own metrics
You can add application-level metrics in your code by using prometheus_client directly. The exporter is global and will pick up your metrics.
To add metrics to the Django internals, the easiest way is to extend django-prometheus' classes. Please consider contributing your metrics, pull requests are welcome. Make sure to read the Prometheus best practices on instrumentation and naming.
Importing Django Prometheus using only local settings
If you wish to use Django Prometheus but are not able to change the code base, it's possible to have all the default metrics by modifying only the settings.
First step is to inject prometheus' middlewares and to add django_prometheus in INSTALLED_APPS
MIDDLEWARE = \
['django_prometheus.middleware.PrometheusBeforeMiddleware'] + \
MIDDLEWARE + \
['django_prometheus.middleware.PrometheusAfterMiddleware']
INSTALLED_APPS += ['django_prometheus']
Second step is to create the /metrics end point, for that we need another file (called urls_prometheus_wrapper.py in this example) that will wraps the apps URLs and add one on top:
from django.conf.urls import include, url
urlpatterns = []
urlpatterns.append(url('prometheus/', include('django_prometheus.urls')))
urlpatterns.append(url('', include('myapp.urls')))
This file will add a "/prometheus/metrics" end point to the URLs of django that will export the metrics (replace myapp by your project name).
Then we inject the wrapper in settings:
ROOT_URLCONF = "graphite.urls_prometheus_wrapper"
Adding custom labels to middleware (request/response) metrics
You can add application specific labels to metrics reported by the django-prometheus middleware. This involves extending the classes defined in middleware.py.
- Extend the Metrics class and override the
register_metricmethod to add the application specific labels. - Extend middleware classes, set the metrics_cls class attribute to the the extended metric class and override the label_metric method to attach custom metrics.
See implementation example in the test app
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file django-prometheus-2.1.0.dev48.tar.gz.
File metadata
- Download URL: django-prometheus-2.1.0.dev48.tar.gz
- Upload date:
- Size: 21.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.2 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | a4f05ff328f0c2ff5de0c9b856656174aa6ad4e84c72e02cdd27350ae37ccabf |
|
| MD5 | a0d9aa22dc2b425e9876be2e27b08f64 |
|
| BLAKE2b-256 | 0c3d5720ea36b4b77e74756bf4769c10581373660258f11813bdf0d32b7fbc00 |
File details
Details for the file django_prometheus-2.1.0.dev48-py2.py3-none-any.whl.
File metadata
- Download URL: django_prometheus-2.1.0.dev48-py2.py3-none-any.whl
- Upload date:
- Size: 28.8 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.2 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 1fa1327a22f2f8cfd962e5d236bbf82d42b1ea7c130c3f12a6049123d1aef6d6 |
|
| MD5 | 5998b9ba6ef81f1653ac38a87a8a8c0e |
|
| BLAKE2b-256 | 82cb879d1b8a47a3fcfa03399442302fa0a8dfc3d7fa6613b829fd1d39551019 |
