The current backend code doesn't honor the minimum interval set in the UI for alerts using the Elasticsearch data source. This means that the data the alerts are triggering against will never match the data in the visualization if auto is used in the date histogram as interval. This fixes the problem to make sure that date histogram auto interval is set according to min interval set in UI for the query or fallback to data source min interval setting. Fixes #22082 Co-authored-by: Marcus Efraimsson <marcus.efraimsson@gmail.com>
Name |
Last commit
|
Last Update |
---|---|---|
.. | ||
azuremonitor | Loading commit data... | |
cloudmonitoring | Loading commit data... | |
cloudwatch | Loading commit data... | |
elasticsearch | Loading commit data... | |
graphite | Loading commit data... | |
influxdb | Loading commit data... | |
mssql | Loading commit data... | |
mysql | Loading commit data... | |
opentsdb | Loading commit data... | |
postgres | Loading commit data... | |
prometheus | Loading commit data... | |
sqleng | Loading commit data... | |
testdatasource | Loading commit data... | |
fake_test.go | Loading commit data... | |
frame_util.go | Loading commit data... | |
interval.go | Loading commit data... | |
interval_test.go | Loading commit data... | |
models.go | Loading commit data... | |
query_endpoint.go | Loading commit data... | |
request.go | Loading commit data... | |
request_test.go | Loading commit data... | |
time_range.go | Loading commit data... | |
time_range_test.go | Loading commit data... |