django-elasticsearch-metrics 2026.0.6

Django app for storing time-series metrics in Elasticsearch.

django-elasticsearch-metrics ("djelme" for short)

Django app for storing time-series metrics in Elasticsearch.

django-elasticsearch-metrics on pypi: https://pypi.org/project/django-elasticsearch-metrics

python importables:

• elasticsearch_metrics
• elasticsearch_metrics.imps.elastic8 (an implementation with elasticsearch 8)
• ...

Pre-requisites

• Python >=3.10
• Django 4.2, 5.1, or 5.2
• Elasticsearch 8

Install

pip install django-elasticsearch-metrics

Quickstart

Add "elasticseach_metrics" to INSTALLED_APPS.

# ... in your django project settings.py ...
INSTALLED_APPS += ["elasticsearch_metrics"]

Configure at least one djelme backend:

# ... in your django project settings.py ...
DJELME_BACKENDS = {
    "my-es8-backend": {  # a name from and for you 
        "elasticsearch_metrics.imps.elastic8": {  # importable djelme implementation
            # dictionary of kwargs for the imp's `djelme_backend` constructor
            # (in this case passed thru as kwargs to `elasticsearch8.Elasticsearch`)
            "hosts": "https://my-elastic8.example:9200",
        },
    },
}

In one of your apps, add record types in metrics.py

# myapp/metrics.py

from elasticsearch_metrics.imps.elastic8 import EventRecord


class UsageEvent(EventRecord):
    item_id: int

    class Index:
        using = "my-es8-backend"  # backend name -- required if multiple backends use the same imp

and be sure to run the djelme_backend_setup management command before trying to store anything:

# This will create an index template for each timeseries record type
python manage.py djelme_backend_setup

Now add some data:

from myapp.metrics import UsageEvent

# By default we create an index for each day.
# Therefore, this will persist the document
# to an index named for the record type and date
UsageEvent.record(item_id='my.item.id')

Go forth and search!

# get an instance of `elasticsearch8.dsl.Search` that queries all timeseries indexes of this type:
UsageEvent.search()

# or get a `Search` for a given time range (from_when <= timestamp < until_when)
UsageEvent.search_timeseries_range((1999,), (2001,))  # in or after 1999; before 2001
UsageEvent.search_timeseries_range((2050, 12), (2051,))  # in 2050-12
UsageEvent.search_timeseries_range(datetime.date(2030, 1, 1), datetime.date(2030, 2, 1))  # in 2030-01

Timeseries indexes

By default, behind the scenes, a new elasticsearch index is created for each record type for each day in which a record is saved (using UTC timezone). You can change this for a record type by setting Meta.timeseries_index_timedepth, or change the default timedepth with the setting DJELME_DEFAULT_TIMEDEPTH (see below).

class MyEventWithMonthlyIndexes(EventRecord):
    class Meta:
        timeseries_index_timedepth = 2  # year and month

• index per year: timeseries_index_timedepth = 1
• index per month: timeseries_index_timedepth = 2
• index per day: timeseries_index_timedepth = 3 (default)
• index per hour: timeseries_index_timedepth = 4

Index settings

You can configure the index settings that will be set on the index template and used for each new timeseries index with Index.settings on a record type.

class UsageEvent(EventRecord):
    item_id: int

    class Index:
        settings = {"number_of_shards": 2, "refresh_interval": "5s"}

Index templates

Each record type will have its own index template. The index template name and glob pattern are computed from the app label for the containing app and the class's name. For example, a UsageEvent class defined in myapp/metrics.py will have an index template with the name myapp_usagerecord and a template glob pattern of myapp_usagerecord_*.

If you declare a record type outside of an app, you will need to set app_label.

class UsageEvent(EventRecord):
    class Meta:
        app_label = "myapp"

Alternatively, you can set template_name and/or template explicitly.

class UsageEvent(EventRecord):
    item_id: int

    class Meta:
        template_name = "myapp_pviews"
        template = "myapp_pviews_*"

Abstract record types

from elasticsearch_metrics.imps.elastic8 import EventRecord


class MyBaseMetric(EventRecord):
    item_id: int

    class Meta:
        abstract = True


class UsageEvent(MyBaseMetric):
    class Meta:
        app_label = "myapp"

Configuration

• DJELME_BACKENDS: Named backends for storing or searching records from your django app -- nested mapping from backend name (any string, your choice) to python-importable paths for modules that (like "elasticsearch_metrics.imps.elastic8") to "imp kwargs" config dictionaries given to the imp module's djelme_backend constructor

  # ... in your django project settings.py ...
  DJELME_BACKENDS = {
      "my-es8-backend": {  # a name from and for you 
          "elasticsearch_metrics.imps.elastic8": {  # importable djelme implementation
              # dictionary of kwargs for the imp's `djelme_backend` constructor
              # (in this case passed thru as kwargs to `elasticsearch8.Elasticsearch`)
              "hosts": "https://my-elastic8.example:9200",
          },
      },
  }
  

• DJELME_DEFAULT_TIMEDEPTH: Set the granularity of timeseries indexes by the number of "time parts" in index names

  DJELME_DEFAULT_TIMEDEPTH = 1  # yearly indexes; YYYY
  DJELME_DEFAULT_TIMEDEPTH = 2  # monthly indexes; YYYY.MM
  DJELME_DEFAULT_TIMEDEPTH = 3  # daily indexes; YYYY.MM.DD (this is the default)
  DJELME_DEFAULT_TIMEDEPTH = 4  # hourly indexes; YYYY.MM.DD.HH
  

  you can also set Meta.timeseries_index_timedepth on a specific record type; this will take precedence

Management commands

• djelme_backend_types: Pretty-print a listing of all registered record types.
• djelme_backend_setup: Ensure that index templates have been created for your record types.
• djelme_backend_check: Check if index templates are in sync. Exits with an error code if any templates are out of sync.
• djelme_indexes: Inspect existing indexes and (with --delete-expired) delete expired indexes

Signals

Signals are located in the elasticsearch_metrics.signals module.

• pre_index_template_create(Metric, index_template, using): Sent before PUTting a new index template into Elasticsearch.
• post_index_template_create(Metric, index_template, using): Sent after PUTting a new index template into Elasticsearch.
• pre_save(Metric, instance, using, index): Sent at the beginning of a Metric's save() method.
• post_save(Metric, instance, using, index): Sent at the end of a Metric's save() method.

Resources

• Elasticsearch as a Time Series Data Store
• Pythonic Analytics with Elasticsearch
• In Search of Agile Time Series Database

License

MIT Licensed.