grafana

mirror of https://github.com/grafana/grafana.git synced 2025-09-21 08:02:27 +08:00

Files

Jorge Luis Betancourt e4f2006cce Elasticsearch: Fix calculation of trimEdges (#56148 )

* Elasticsearch: Fix calculation of trimEdges

When a value of trimEdges is set greater than 1 we need to drop both the
first and last sample of the data from the response.

* Elasticsearch: Fix reading trimEdges from the query settings

Currently the trimEdges property in the JSON panel is stored as a string
and not directly as a number.

This caused that the reading of the value failed in the go backend
because the simplejson.Int() method doesn't properly handle this case.
This failure when decoding the value goes unnoticed because of the early
return causing the trimEdges configuration to be ignored.

* Refactor castToInt to also return an error

Add a new test case that sets the `trimEdges` property as a quoted
number.

2022-10-14 12:53:12 +02:00

client

Elasticsearch: Reuse http client in the backend (#55172 )

2022-09-26 14:27:46 +02:00

elasticsearch_test.go

Elasticsearch: Reuse http client in the backend (#55172 )

2022-09-26 14:27:46 +02:00

elasticsearch.go

Elasticsearch: Reuse http client in the backend (#55172 )

2022-09-26 14:27:46 +02:00

models.go

IntervalV2: Use maxDataPoints to calculate correct interval (#39036 )