# django-prometheus
Export Django monitoring metrics for Prometheus.io
[](https://gitter.im/django-prometheus/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](http://badge.fury.io/py/django-prometheus)
[](https://github.com/korfuri/django-prometheus/actions/workflows/ci.yml)
[](https://coveralls.io/github/korfuri/django-prometheus?branch=master)
[](https://pypi.python.org/pypi/django-prometheus)
[](https://github.com/psf/black)
## Features
This library provides Prometheus metrics for Django related operations:
* Requests & Responses
* Database access done via [Django ORM](https://docs.djangoproject.com/en/3.2/topics/db/)
* Cache access done via [Django Cache framework](https://docs.djangoproject.com/en/3.2/topics/cache/)
## Usage
### Requirements
* Django >= 3.2
* Python 3.7 and above.
### Installation
Install with:
```shell
pip install django-prometheus
```
Or, if you're using a development version cloned from this repository:
```shell
python path-to-where-you-cloned-django-prometheus/setup.py install
```
This will install [prometheus_client](https://github.com/prometheus/client_python) as a dependency.
### Quickstart
In your settings.py:
```python
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:
```python
urlpatterns = [
...
path('', include('django_prometheus.urls')),
]
```
### Configuration
Prometheus uses Histogram based grouping for monitoring latencies. The default
buckets are:
```python
PROMETHEUS_LATENCY_BUCKETS = (0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1.0, 2.5, 5.0, 7.5, 10.0, 25.0, 50.0, 75.0, float("inf"),)
```
You can define custom buckets for latency, adding more buckets decreases performance but
increases accuracy: <https://prometheus.io/docs/practices/histograms/>
```python
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`.
```python
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`.
```python
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:
```python
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:
```python
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](https://github.com/prometheus/client_python)
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](http://prometheus.io/docs/practices/instrumentation/)
and [naming](http://prometheus.io/docs/practices/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
```python
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:
```python
from django.urls import include, path
urlpatterns = []
urlpatterns.append(path('prometheus/', include('django_prometheus.urls')))
urlpatterns.append(path('', 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:
```python
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_metric` method 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](django_prometheus/tests/end2end/testapp/test_middleware_custom_labels.py#L19-L46)
Raw data
{
"_id": null,
"home_page": "http://github.com/korfuri/django-prometheus",
"name": "django-prometheus",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "django monitoring prometheus",
"author": "Uriel Corfa",
"author_email": "uriel@corfa.fr",
"download_url": "https://files.pythonhosted.org/packages/e1/51/485b4122e00f2b8efec8a6d718ef4ce6b150231e49398e554ce1151f65c3/django-prometheus-2.3.1.tar.gz",
"platform": null,
"description": "# django-prometheus\n\nExport Django monitoring metrics for Prometheus.io\n\n[](https://gitter.im/django-prometheus/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n\n[](http://badge.fury.io/py/django-prometheus)\n[](https://github.com/korfuri/django-prometheus/actions/workflows/ci.yml)\n[](https://coveralls.io/github/korfuri/django-prometheus?branch=master)\n[](https://pypi.python.org/pypi/django-prometheus)\n[](https://github.com/psf/black)\n\n## Features\n\nThis library provides Prometheus metrics for Django related operations:\n\n* Requests & Responses\n* Database access done via [Django ORM](https://docs.djangoproject.com/en/3.2/topics/db/)\n* Cache access done via [Django Cache framework](https://docs.djangoproject.com/en/3.2/topics/cache/)\n\n## Usage\n\n### Requirements\n\n* Django >= 3.2\n* Python 3.7 and above.\n\n### Installation\n\nInstall with:\n\n```shell\npip install django-prometheus\n```\n\nOr, if you're using a development version cloned from this repository:\n\n```shell\npython path-to-where-you-cloned-django-prometheus/setup.py install\n```\n\nThis will install [prometheus_client](https://github.com/prometheus/client_python) as a dependency.\n\n### Quickstart\n\nIn your settings.py:\n\n```python\nINSTALLED_APPS = [\n ...\n 'django_prometheus',\n ...\n]\n\nMIDDLEWARE = [\n 'django_prometheus.middleware.PrometheusBeforeMiddleware',\n # All your other middlewares go here, including the default\n # middlewares like SessionMiddleware, CommonMiddleware,\n # CsrfViewmiddleware, SecurityMiddleware, etc.\n 'django_prometheus.middleware.PrometheusAfterMiddleware',\n]\n```\n\nIn your urls.py:\n\n```python\nurlpatterns = [\n ...\n path('', include('django_prometheus.urls')),\n]\n```\n\n### Configuration\n\nPrometheus uses Histogram based grouping for monitoring latencies. The default\nbuckets are:\n\n```python\nPROMETHEUS_LATENCY_BUCKETS = (0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1.0, 2.5, 5.0, 7.5, 10.0, 25.0, 50.0, 75.0, float(\"inf\"),)\n```\n\nYou can define custom buckets for latency, adding more buckets decreases performance but\nincreases accuracy: <https://prometheus.io/docs/practices/histograms/>\n\n```python\nPROMETHEUS_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\"))\n```\n\n### Monitoring your databases\n\nSQLite, MySQL, and PostgreSQL databases can be monitored. Just\nreplace the `ENGINE` property of your database, replacing\n`django.db.backends` with `django_prometheus.db.backends`.\n\n```python\nDATABASES = {\n 'default': {\n 'ENGINE': 'django_prometheus.db.backends.sqlite3',\n 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),\n },\n}\n```\n\n### Monitoring your caches\n\nFilebased, memcached, redis caches can be monitored. Just replace\nthe cache backend to use the one provided by django_prometheus\n`django.core.cache.backends` with `django_prometheus.cache.backends`.\n\n```python\nCACHES = {\n 'default': {\n 'BACKEND': 'django_prometheus.cache.backends.filebased.FileBasedCache',\n 'LOCATION': '/var/tmp/django_cache',\n }\n}\n```\n\n### Monitoring your models\n\nYou may want to monitor the creation/deletion/update rate for your\nmodel. This can be done by adding a mixin to them. This is safe to do\non existing models (it does not require a migration).\n\nIf your model is:\n\n```python\nclass Dog(models.Model):\n name = models.CharField(max_length=100, unique=True)\n breed = models.CharField(max_length=100, blank=True, null=True)\n age = models.PositiveIntegerField(blank=True, null=True)\n```\n\nJust add the `ExportModelOperationsMixin` as such:\n\n```python\nfrom django_prometheus.models import ExportModelOperationsMixin\n\nclass Dog(ExportModelOperationsMixin('dog'), models.Model):\n name = models.CharField(max_length=100, unique=True)\n breed = models.CharField(max_length=100, blank=True, null=True)\n age = models.PositiveIntegerField(blank=True, null=True)\n```\n\nThis will export 3 metrics, `django_model_inserts_total{model=\"dog\"}`,\n`django_model_updates_total{model=\"dog\"}` and\n`django_model_deletes_total{model=\"dog\"}`.\n\nNote that the exported metrics are counters of creations,\nmodifications and deletions done in the current process. They are not\ngauges of the number of objects in the model.\n\nStarting with Django 1.7, migrations are also monitored. Two gauges\nare exported, `django_migrations_applied_by_connection` and\n`django_migrations_unapplied_by_connection`. You may want to alert if\nthere are unapplied migrations.\n\nIf you want to disable the Django migration metrics, set the\n`PROMETHEUS_EXPORT_MIGRATIONS` setting to False.\n\n### Monitoring and aggregating the metrics\n\nPrometheus is quite easy to set up. An example prometheus.conf to\nscrape `127.0.0.1:8001` can be found in `examples/prometheus`.\n\nHere's an example of a PromDash displaying some of the metrics\ncollected by django-prometheus:\n\n\n\n## Adding your own metrics\n\nYou can add application-level metrics in your code by using\n[prometheus_client](https://github.com/prometheus/client_python)\ndirectly. The exporter is global and will pick up your metrics.\n\nTo add metrics to the Django internals, the easiest way is to extend\ndjango-prometheus' classes. Please consider contributing your metrics,\npull requests are welcome. Make sure to read the Prometheus best\npractices on\n[instrumentation](http://prometheus.io/docs/practices/instrumentation/)\nand [naming](http://prometheus.io/docs/practices/naming/).\n\n## Importing Django Prometheus using only local settings\n\nIf you wish to use Django Prometheus but are not able to change\nthe code base, it's possible to have all the default metrics by\nmodifying only the settings.\n\nFirst step is to inject prometheus' middlewares and to add\ndjango_prometheus in INSTALLED_APPS\n\n```python\nMIDDLEWARE = \\\n ['django_prometheus.middleware.PrometheusBeforeMiddleware'] + \\\n MIDDLEWARE + \\\n ['django_prometheus.middleware.PrometheusAfterMiddleware']\n\nINSTALLED_APPS += ['django_prometheus']\n```\n\nSecond step is to create the /metrics end point, for that we need\nanother file (called urls_prometheus_wrapper.py in this example) that\nwill wraps the apps URLs and add one on top:\n\n```python\nfrom django.urls import include, path\n\n\nurlpatterns = []\n\nurlpatterns.append(path('prometheus/', include('django_prometheus.urls')))\nurlpatterns.append(path('', include('myapp.urls')))\n```\n\nThis file will add a \"/prometheus/metrics\" end point to the URLs of django\nthat will export the metrics (replace myapp by your project name).\n\nThen we inject the wrapper in settings:\n\n```python\nROOT_URLCONF = \"graphite.urls_prometheus_wrapper\"\n```\n\n## Adding custom labels to middleware (request/response) metrics\n\nYou can add application specific labels to metrics reported by the django-prometheus middleware.\nThis involves extending the classes defined in middleware.py.\n\n* Extend the Metrics class and override the `register_metric` method to add the application specific labels.\n* 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.\n\nSee implementation example in [the test app](django_prometheus/tests/end2end/testapp/test_middleware_custom_labels.py#L19-L46)\n",
"bugtrack_url": null,
"license": "Apache",
"summary": "Django middlewares to monitor your application with Prometheus.io.",
"version": "2.3.1",
"project_urls": {
"Changelog": "https://github.com/korfuri/django-prometheus/blob/master/CHANGELOG.md",
"Documentation": "https://github.com/korfuri/django-prometheus/blob/master/README.md",
"Homepage": "http://github.com/korfuri/django-prometheus",
"Source": "https://github.com/korfuri/django-prometheus",
"Tracker": "https://github.com/korfuri/django-prometheus/issues"
},
"split_keywords": [
"django",
"monitoring",
"prometheus"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "3a75fb3d4f056f9ed4f8848817d5afd7a1d949632ab117452ccd179e3839cfc4",
"md5": "f8c69c768afbf587fc75c20cbbf98c0f",
"sha256": "cf9b26f7ba2e4568f08f8f91480a2882023f5908579681bcf06a4d2465f12168"
},
"downloads": -1,
"filename": "django_prometheus-2.3.1-py2.py3-none-any.whl",
"has_sig": false,
"md5_digest": "f8c69c768afbf587fc75c20cbbf98c0f",
"packagetype": "bdist_wheel",
"python_version": "py2.py3",
"requires_python": null,
"size": 29081,
"upload_time": "2023-05-02T19:53:20",
"upload_time_iso_8601": "2023-05-02T19:53:20.421950Z",
"url": "https://files.pythonhosted.org/packages/3a/75/fb3d4f056f9ed4f8848817d5afd7a1d949632ab117452ccd179e3839cfc4/django_prometheus-2.3.1-py2.py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "e151485b4122e00f2b8efec8a6d718ef4ce6b150231e49398e554ce1151f65c3",
"md5": "c27fb578a8d1092a1b47018dad12243b",
"sha256": "f9c8b6c780c9419ea01043c63a437d79db2c33353451347894408184ad9c3e1e"
},
"downloads": -1,
"filename": "django-prometheus-2.3.1.tar.gz",
"has_sig": false,
"md5_digest": "c27fb578a8d1092a1b47018dad12243b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 24718,
"upload_time": "2023-05-02T19:53:58",
"upload_time_iso_8601": "2023-05-02T19:53:58.420182Z",
"url": "https://files.pythonhosted.org/packages/e1/51/485b4122e00f2b8efec8a6d718ef4ce6b150231e49398e554ce1151f65c3/django-prometheus-2.3.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-05-02 19:53:58",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "korfuri",
"github_project": "django-prometheus",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "django-redis",
"specs": [
[
">=",
"4.12.1"
]
]
},
{
"name": "prometheus-client",
"specs": [
[
">=",
"0.12.0"
]
]
},
{
"name": "pip-prometheus",
"specs": [
[
">=",
"1.2.1"
]
]
},
{
"name": "mysqlclient",
"specs": []
},
{
"name": "psycopg2",
"specs": []
},
{
"name": "pytest",
"specs": [
[
"==",
"7.4.3"
]
]
},
{
"name": "pytest-django",
"specs": []
},
{
"name": "pylibmc",
"specs": []
},
{
"name": "pymemcache",
"specs": []
},
{
"name": "python-memcached",
"specs": []
},
{
"name": "setuptools",
"specs": [
[
"<",
"72.0.0"
]
]
},
{
"name": "wheel",
"specs": []
}
],
"tox": true,
"lcname": "django-prometheus"
}
JSON
