Hi,
First off: thank you for Prompage. It is a fantastic little application.
There’s a small “surprising default” in the graph settings that leads to silent data truncation and a confusing visual result.
Current defaults:
services.query.range: 24hservices.query.step: 5mui.graphs.points: 200
With those values, the query returns:
24h / 5m = 288 data points
Since the graph is capped at 200 points, the last ~88 points aren’t shown. With a 5-minute step, that’s:
88 × 5 minutes = 440 minutes ≈ 7h 20m
Observed behavior
On the service graph page, the rightmost x-axis never reaches “now”. It initially looked like the graph was shown in a different timezone (about ~7-8 hours off), but it turns out it’s missing the newest samples.
Suggestion
Either:
- increase the default
ui.graphs.points to at least 288 (or higher), or
- adjust the default range/step so the default query stays within the default max points, or
- (optionally) change the condensing/truncation behavior so it preserves the most recent data (e.g., keep the last N points, or bucket evenly).
Thanks again for the project — hope this is helpful.
Best regards,
eKristensen
Hi,
First off: thank you for Prompage. It is a fantastic little application.
There’s a small “surprising default” in the graph settings that leads to silent data truncation and a confusing visual result.
Current defaults:
services.query.range: 24hservices.query.step: 5mui.graphs.points: 200With those values, the query returns:
24h / 5m = 288data pointsSince the graph is capped at 200 points, the last ~88 points aren’t shown. With a 5-minute step, that’s:
88 × 5 minutes = 440 minutes ≈ 7h 20mObserved behavior
On the service graph page, the rightmost x-axis never reaches “now”. It initially looked like the graph was shown in a different timezone (about ~7-8 hours off), but it turns out it’s missing the newest samples.
Suggestion
Either:
ui.graphs.pointsto at least 288 (or higher), orThanks again for the project — hope this is helpful.
Best regards,
eKristensen