Context
SemoTech — self-hosted LogTide v1.3.1, custom dashboard Caddy WAN Geography (geo map, Top-N tables, log table, time series).
Thanks again for the 1.3.x dashboard panel work — we’re live on it. Related: viewport jump filed separately as #304.
Problem
Panel lookback is fixed to a small enum and differs by panel type. There is no global dashboard time picker, and several widgets we use for WAN traffic can’t express common windows like 48h or an arbitrary last N days.
Today (from shared types in 1.3.1):
| Panel |
Field |
Allowed values |
top_n_table |
interval |
1h | 24h | 7d |
geo_map |
interval |
1h | 24h | 7d |
time_series |
interval |
1h | 6h | 24h | 7d | 30d |
log_table |
timeRange |
15m | 1h | 6h | 24h | 7d |
For ops review we often want last 48 hours (or 3d / 14d) on Top Locations / Geo map / Top Blocked without jumping straight to 7d.
Request
- Per-panel timescale control in each widget’s config (already partially there — extend it).
- Ideally also a dashboard-level time range that panels can inherit (with per-panel override), similar to Grafana.
- Broader preset set, e.g.
1h / 6h / 12h / 24h / 48h / 7d / 30d, and/or a custom relative window.
- Align naming (
interval vs timeRange) across panel types if practical.
Acceptance ideas
Happy to test from our Caddy WAN dashboard once this lands.
Context
SemoTech — self-hosted LogTide v1.3.1, custom dashboard Caddy WAN Geography (geo map, Top-N tables, log table, time series).
Thanks again for the 1.3.x dashboard panel work — we’re live on it. Related: viewport jump filed separately as #304.
Problem
Panel lookback is fixed to a small enum and differs by panel type. There is no global dashboard time picker, and several widgets we use for WAN traffic can’t express common windows like 48h or an arbitrary last N days.
Today (from shared types in 1.3.1):
top_n_tableinterval1h|24h|7dgeo_mapinterval1h|24h|7dtime_seriesinterval1h|6h|24h|7d|30dlog_tabletimeRange15m|1h|6h|24h|7dFor ops review we often want last 48 hours (or 3d / 14d) on Top Locations / Geo map / Top Blocked without jumping straight to 7d.
Request
1h/6h/12h/24h/48h/7d/30d, and/or a custom relative window.intervalvstimeRange) across panel types if practical.Acceptance ideas
top_n_tableandgeo_mapsupport at least48h(or custom relative range)Happy to test from our Caddy WAN dashboard once this lands.