A querying chart offers its own windows: an optional ranges list of {label, range_s, interval_s}, up to 8 and checked by the server, where range_s 0 asks for the whole history; the editor lists and picks them, and the refresh is capped at what a timer can hold
This commit is contained in:
@@ -188,6 +188,21 @@ Choose the chart's data source:
|
||||
|
||||
Multi-line charts show a legend as well as different colours.
|
||||
|
||||
A Query chart offers 1h, 6h, 24h and 7d down its right-hand edge, and opens on
|
||||
24h. Under **Ranges** you can give it windows of its own instead, up to eight,
|
||||
and it opens on the one its `range_s` names or else the first. Each window
|
||||
becomes the request's `range_s` and `interval_s` when picked. A `range_s` of
|
||||
`0` asks for the whole history, and the answering flow decides how far back
|
||||
that reaches.
|
||||
|
||||
```json
|
||||
"ranges": [
|
||||
{"label": "1M", "range_s": 2592000, "interval_s": 86400},
|
||||
{"label": "1Y", "range_s": 31536000, "interval_s": 86400},
|
||||
{"label": "All", "range_s": 0, "interval_s": 86400}
|
||||
]
|
||||
```
|
||||
|
||||
!!! tip "Skip the unfinished bucket"
|
||||
|
||||
If your query aggregates into time buckets, leave out the bucket still
|
||||
|
||||
Reference in New Issue
Block a user