The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.

prometheushacktoberfestmetricsmonitoringalertinggrafanagoinfluxdbmysqlpostgresanalyticsdata-visualizationdashboardbusiness-intelligenceelasticsearch

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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.		3 years ago
..
client	Elasticsearch: Reuse http client in the backend (#55172)	3 years ago
elasticsearch.go	Elasticsearch: Reuse http client in the backend (#55172)	3 years ago
elasticsearch_test.go	Elasticsearch: Reuse http client in the backend (#55172)	3 years ago
models.go	IntervalV2: Use maxDataPoints to calculate correct interval (#39036)	4 years ago
response_parser.go	Elasticsearch: Fix calculation of trimEdges (#56148)	3 years ago
response_parser_test.go	Elasticsearch: Fix calculation of trimEdges (#56148)	3 years ago
time_series_query.go	elastic: always use millisecond-intervals for alerting (#54157)	3 years ago
time_series_query_test.go	elastic: always use millisecond-intervals for alerting (#54157)	3 years ago