0
Feature request: relative time ranges on stats endpoints (so static dashboards need no proxy)
Source: umami-software/umami#4547 · opened by @Infinifar
API keys in v3.4 (#4454) solved authentication for stateless dashboards — thank you.
One blocker remains for tools like Homepage (gethomepage.dev): GET /api/websites/{id}/stats still requires a dynamic startAt+endAt (or startDate+endDate). Such dashboards use static config URLs and cannot compute timestamps at request time, so they still require a sidecar proxy to render analytics.
Suggestion: accept a relative range parameter, e.g. ?period=24h (today, 7d, 30d), or default to a range when none is provided.
That would let a static dashboard do:
One blocker remains for tools like Homepage (gethomepage.dev): GET /api/websites/{id}/stats still requires a dynamic startAt+endAt (or startDate+endDate). Such dashboards use static config URLs and cannot compute timestamps at request time, so they still require a sidecar proxy to render analytics.
Suggestion: accept a relative range parameter, e.g. ?period=24h (today, 7d, 30d), or default to a range when none is provided.
That would let a static dashboard do:
No pledges yet. Be the first to back this.
Comments
Similar requests
API to read traefik log passed through telegraf
2 votes · 0 comments
Stats percentages are calculated with wrong reference timeframe
0 votes · 0 comments
[Feature Request] Option to Disable Page and Referrals from Share URL Stats
1 vote · 0 comments
Feature Request: Sharing dashboards with other users
1 vote · 0 comments
Get the full URL for "page" rather than the relative one
1 vote · 0 comments
No comments yet.