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_test.go

SQL: Migrate to use SDK contracts (#36635)

2021-09-07 09:35:37 +02:00

client.go

change log level to debug (#41102)

2021-11-01 09:00:00 +00:00

index_pattern_test.go

Plugins: Migrate Elasticsearch to backend plugin SDK (#36132)

2021-07-15 16:45:59 +02:00

index_pattern.go

Plugins: Migrate Elasticsearch to backend plugin SDK (#36132)

2021-07-15 16:45:59 +02:00

models.go

Elastic: Allow using long/int as date field for alerts (#44027)

2022-01-17 15:45:09 +01:00

search_request_test.go

Elastic: Allow using long/int as date field for alerts (#44027)

2022-01-17 15:45:09 +01:00

search_request.go

Elastic: Allow using long/int as date field for alerts (#44027)

2022-01-17 15:45:09 +01:00