-
Logs: Use result range instead of timepicker range for log histogram (#25027) · 57abf39f
* Logs: Use result range instead of timepicker range for log histogram If a logs datasource does not send histogram data for the requested time range, the logs model computes a timeseries based on the log row counts, bucketed by an automcatically calculated time interval. Even when this histogram time series did not span the whole requested time range it was still rendered in the graph across the whole range, leaving an empty area at its start. Users find this confusing and are lead to believe their log data is missing. This change fixes this by anchoring the start of the timeseries on the first log row's timestamp from the result, and adds this smaller range as `visibleRange` to the logs model and passes it through to the logs component that optionally takes it into account to not render the empty area. The interval (bucket size) is also adjusted to account for a potentially finer resolution on the shorter visible time interval. The bucketsize multiplier was also changed from 10 to 20 to account for the space between the chart's bars. * Aligned visible range with buckets * Extract bucket size calculation and add test
David committed
Name |
Last commit
|
Last Update |
---|---|---|
.. | ||
core | Loading commit data... | |
features | Loading commit data... | |
partials | Loading commit data... | |
plugins | Loading commit data... | |
routes | Loading commit data... | |
store | Loading commit data... | |
types | Loading commit data... | |
app.ts | Loading commit data... | |
dev.ts | Loading commit data... | |
index.ts | Loading commit data... |