mirror of
https://github.com/grafana/grafana.git
synced 2025-02-12 00:25:46 -06:00
e4f2006cce
* 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. |
||
|---|---|---|
| .. | ||
| azuremonitor | ||
| cloudmonitoring | ||
| cloudwatch | ||
| elasticsearch | ||
| grafanads | ||
| graphite | ||
| influxdb | ||
| intervalv2 | ||
| legacydata | ||
| loki | ||
| mssql | ||
| mysql | ||
| opentsdb | ||
| postgres | ||
| prometheus | ||
| sqleng | ||
| tempo | ||
| testdatasource | ||