Name |
Last commit
|
Last Update |
---|---|---|
.. | ||
dashboards | ||
img | ||
partials | ||
specs | ||
README.md | ||
datasource.ts | ||
metric_find_query.d.ts | ||
metric_find_query.js | ||
module.ts | ||
plugin.json | ||
query_ctrl.ts |
Previously `Step` parameter would set a hard value for any zoom level. Now it's renamed to `Min step` and sets the minimal value of `step` parameter to Prometheus query. User would usually want to set it to the scraping interval of the target metric to avoid having shap cliffs on graphs and extra load on Prometheus. Actual `step` value is calculated as the minimum of automatically selected step (based on zoom level) and user provided minimal step. If user did not provide the step, then automatic value is used as is. Example bahavior for `60s` scrape intervals: * `5s` automatic interval, no user specified min step: * Before: `step=5` * After: `step=5` * `5s` automatic interval, `1m` user specified min step: * Before: `step=5` * After: `step=60` * `5m` automatic interval, `1m` user specified min step: * Before: `step=60` (not really visible, too dense) * After: `step=300` (automatic value is picked) See: * https://github.com/grafana/grafana/issues/8065 * https://github.com/prometheus/prometheus/issues/2564
Name |
Last commit
|
Last Update |
---|---|---|
.. | ||
dashboards | Loading commit data... | |
img | Loading commit data... | |
partials | Loading commit data... | |
specs | Loading commit data... | |
README.md | Loading commit data... | |
datasource.ts | Loading commit data... | |
metric_find_query.d.ts | Loading commit data... | |
metric_find_query.js | Loading commit data... | |
module.ts | Loading commit data... | |
plugin.json | Loading commit data... | |
query_ctrl.ts | Loading commit data... |