PUT /testing-timeseries-mode
{
"settings": {
"index": {
"routing_path": [
"dimension-1",
"dimension-2"
],
"mode": "time_series"
}
},
"mappings": {
"properties": {
"counter-field": {
"type": "integer",
"time_series_metric": "counter"
},
"dimension-1": {
"type": "keyword",
"time_series_dimension": true
},
"dimension-2": {
"type": "keyword",
"time_series_dimension": true
}
}
}
}
POST testing-timeseries-mode/_doc/
{
"@timestamp": "2099-11-15T13:12:00",
"counter-field": 123
}
POST testing-timeseries-mode/_doc/
{
"@timestamp": "2099-11-15T13:12:00",
"counter-field": 123,
"dimension-1": "AA"
}
POST testing-timeseries-mode/_doc/
{
"@timestamp": "2099-11-15T13:12:00",
"counter-field": 321,
"dimension-1": "AA"
}
POST testing-timeseries-mode/_doc/
{
"@timestamp": "2099-11-15T13:12:00",
"counter-field": 321,
"dimension-1": "AA",
"dimension-2": "BB"
}
TSDB feature has been introduced since 8.5. Goal is to enable TSDB with latest Kubernetes Integration package and validate functionality of collection, ingestion and visualisation of Kubernetes resources.
Relevant information can be found here.
Goal*
Validate Kubernetes Integration functionality and UX with TSDB feature enabled
TSDB very simple example
Steps to reproduce the example
routing_path:It should fail:

3. Adding a document with a unique combination between timestamp and dimension should work:
counter-fieldvalue, then it will fail because the combination already exists:Outcomes:
Dimensionfields, if they are accurate for TSDb configurationhttps://github.com/elastic/rally-tracks/tree/master/tsdb : Specific Track for TSDB
https://github.com/elastic/k8s-integration-infra/tree/cloudnative/cloudnative : Track with data focused on K8s integration
Breaking the steps of the Story:
For the future:
index_mode: "time_series"