grafana/pkg/tsdb/elasticsearch
Piotr Jamróz 9fb8339f87
Elastic: Allow using long/int as date field for alerts (#44027)
* Use integers for time range filter

Previously it was passed as a string which is automatically converted by Elastic to a number only if the field type is "date". For other types (e.g. "long") such conversion doesn't work. In theory "date" could be passed as a formatted string but we don't use it this way and always pass it as a number so it is safe to always pass numbers, not strings.

* Fix time_series_query_test

* Retrigger build
2022-01-17 15:45:09 +01:00
..
client Elastic: Allow using long/int as date field for alerts (#44027) 2022-01-17 15:45:09 +01:00
elasticsearch_test.go Plugins: Migrate Elasticsearch to backend plugin SDK (#36132) 2021-07-15 16:45:59 +02:00
elasticsearch.go add core plugins thru store (#43085) 2021-12-14 15:22:40 +01:00
models.go IntervalV2: Use maxDataPoints to calculate correct interval (#39036) 2021-09-13 14:58:32 +02:00
response_parser_test.go Elasticsearch: Fix metric names for alert queries (#38546) 2021-08-26 09:20:38 +02:00
response_parser.go Chore: Refactor usage of legacy data contracts (#41218) 2021-11-10 11:52:16 +01:00
time_series_query_test.go Elastic: Allow using long/int as date field for alerts (#44027) 2022-01-17 15:45:09 +01:00
time_series_query.go Elastic: Allow using long/int as date field for alerts (#44027) 2022-01-17 15:45:09 +01:00