A time series data stream (TSDS) models timestamped metrics data as one or more time series.
You can use a TSDS to store metrics data more efficiently. In our benchmarks, metrics data stored in a TSDS used 70% less disk space than a regular data stream. The exact impact will vary per data set.
When to use a TSDSedit
Both a regular data stream and a TSDS can store timestamped
metrics data. Only use a TSDS if you typically add metrics data to Elasticsearch in near
A TSDS is only intended for metrics data. For other timestamped data, such as logs or traces, use a regular data stream.
Differences from a regular data streamedit
A TSDS works like a regular data stream with some key differences:
The matching index template for a TSDS requires a
data_streamobject with the
index.mode: time_seriesoption. This option enables most TSDS-related functionality.
In addition to a
@timestamp, each document in a TSDS must contain one or more dimension fields. The matching index template for a TSDS must contain mappings for at least one
TSDS documents also typically contain one or more metric fields.
Elasticsearch generates a hidden
_tsidmetadata field for each document in a TSDS.
- A TSDS uses time-bound backing indices to store data from the same time period in the same backing index.
The matching index template for a TSDS must contain the
index.routing_pathindex setting. A TSDS uses this setting to perform dimension-based routing.
A TSDS uses internal index sorting to order
shard segments by
TSDS documents only support auto-generated document
_idvalues. For TSDS documents, the document
_idis a hash of the document’s dimensions and
@timestamp. A TSDS doesn’t support custom document
A TSDS uses synthetic
_source, and as a result is subject to a number of restrictions.
A time series index can contain fields other than dimensions or metrics.
What is a time series?edit
A time series is a sequence of observations for a specific entity. Together, these observations let you track changes to the entity over time. For example, a time series can track:
- CPU and disk usage for a computer
- The price of a stock
- Temperature and humidity readings from a weather sensor.
In a TSDS, each Elasticsearch document represents an observation, or data point, in a specific time series. Although a TSDS can contain multiple time series, a document can only belong to one time series. A time series can’t span multiple data streams.
Dimensions are field names and values that, in combination, identify a
document’s time series. In most cases, a dimension describes some aspect of the
entity you’re measuring. For example, documents related to the same weather
sensor may always have the same
A TSDS document is uniquely identified by its time series and timestamp, both of
which are used to generate the document
_id. So, two documents with the same
dimensions and the same timestamp are considered to be duplicates. When you use
_bulk endpoint to add documents to a TSDS, a second document with the same
timestamp and dimensions overwrites the first. When you use the
PUT /<target>/_create/<_id> format to add an individual document and a document
with the same
_id already exists, an error is generated.
You mark a field as a dimension using the boolean
mapping parameter. The following field types support the
For a flattened field, use the
time_series_dimensions parameter to configure an array of fields as dimensions. For details refer to
Metrics are fields that contain numeric measurements, as well as aggregations and/or downsampling values based off of those measurements. While not required, documents in a TSDS typically contain one or more metric fields.
Metrics differ from dimensions in that while dimensions generally remain constant, metrics are expected to change over time, even if rarely or slowly.
To mark a field as a metric, you must specify a metric type using the
time_series_metric mapping parameter. The following field types support the
Accepted metric types vary based on the field type:
Valid values for
A cumulative metric that only monotonically increases or resets to
0(zero). For example, a count of errors or completed tasks.
A counter field has additional semantic meaning, because it represents a cumulative counter. This works well with the
rateaggregation, since a rate can be derived from a cumulative monotonically increasing counter. However a number of aggregations (for example
sum) compute results that don’t make sense for a counter field, because of its cumulative nature.
Only numeric and
aggregate_metric_doublefields support the
Due to the cumulative nature of counter fields, the following aggregations are supported and expected to provide meaningful results with the
variable_width_histogram. In order to prevent issues with existing integrations and custom dashboards, we also allow the following aggregations, even if the result might be meaningless on counters:
median absolute deviation,
A metric that represents a single numeric that can arbitrarily increase or decrease. For example, a temperature or available disk space.
Only numeric and
aggregate_metric_doublefields support the
- Not a time series metric.
Time series modeedit
The matching index template for a TSDS must contain a
data_stream object with
index_mode: time_series option. This option ensures the TSDS creates
backing indices with an
index.mode setting of
This setting enables most TSDS-related functionality in the backing indices.
If you convert an existing data stream to a TSDS, only backing indices created
after the conversion have an
time_series. You can’t
index.mode of an existing backing index.
_tsid metadata fieldedit
When you add a document to a TSDS, Elasticsearch automatically generates a
metadata field for the document. The
_tsid is an object containing the
document’s dimensions. Documents in the same TSDS with the same
_tsid are part
of the same time series.
_tsid field is not queryable or updatable. You also can’t retrieve a
_tsid using a get document request. However, you can
_tsid field in aggregations and retrieve the
_tsid value in searches
The format of the
_tsid field shouldn’t be relied upon. It may change
from version to version.
In a TSDS, each backing index, including the most recent backing index, has a
range of accepted
@timestamp values. This range is defined by the
index.time_series.end_time index settings.
When you add a document to a TSDS, Elasticsearch adds the document to the appropriate
backing index based on its
@timestamp value. As a result, a TSDS can add
documents to any TSDS backing index that can receive writes. This applies even
if the index isn’t the most recent backing index.
If no backing index can accept a document’s
@timestamp value, Elasticsearch rejects the
Elasticsearch automatically configures
index.time_series.end_time settings as part of the index creation and rollover
index.look_ahead_time index setting to
configure how far into the future you can add documents to an index. When you
create a new write index for a TSDS, Elasticsearch calculates the index’s
index.time_series.end_time value as:
now + index.look_ahead_time
At the time series poll interval (controlled via
Elasticsearch checks if the write index has met the rollover criteria in its index
lifecycle policy. If not, Elasticsearch refreshes the
now value and updates the write
now + index.look_ahead_time + time_series.poll_interval
This process continues until the write index rolls over. When the index rolls
over, Elasticsearch sets a final
index.time_series.end_time value for the index. This
value borders the
index.time_series.start_time for the new write index. This
@timestamp ranges for neighboring backing indices always border
but never overlap.
Accepted time range for adding dataedit
A TSDS is designed to ingest current metrics data. When the TSDS is first created the initial backing index has:
index.time_series.start_timevalue set to
now - index.look_ahead_time
index.time_series.end_timevalue set to
now + index.look_ahead_time
Only data that falls inside that range can be indexed.
In our TSDS example,
index.look_ahead_time is set to three hours, so only documents with a
@timestamp value that is within three hours previous or subsequent to the
present time are accepted for indexing.
You can use the get data stream API to check the accepted time range for writing to any TSDS.
Within each TSDS backing index, Elasticsearch uses the
index.routing_path index setting to route documents
with the same dimensions to the same shards.
When you create the matching index template for a TSDS, you must specify one or
more dimensions in the
index.routing_path setting. Each document in a TSDS
must contain one or more dimensions that match the
Dimensions in the
index.routing_path setting must be plain
index.routing_path setting accepts wildcard patterns (for example
and can dynamically match new fields. However, Elasticsearch will reject any mapping
updates that add scripted, runtime, or non-dimension, non-
keyword fields that
TSDS documents don’t support a custom
_routing value. Similarly, you can’t
_routing value in mappings for a TSDS.
Elasticsearch uses compression algorithms to compress repeated values. This compression works best when repeated values are stored near each other — in the same index, on the same shard, and side-by-side in the same shard segment.
Most time series data contains repeated values. Dimensions are repeated across documents in the same time series. The metric values of a time series may also change slowly over time.
Internally, each TSDS backing index uses index
sorting to order its shard segments by
@timestamp. This makes it
more likely that these repeated values are stored near each other for better
compression. A TSDS doesn’t support any
index.sort.* index settings.