You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The limit of entries in this issue is due to the resolution of data in the "steps" functionality.
I'd propose to add a parameter in the CLI that allows the user to set the steps in seconds.
In prometheus.go once the selected timeframe goes over 30 Minutes the stepping is calculated by dividing the queried amount of minutes by 4.2. This leads to roughly the same amount of entries once you exceed a 30 minute threshold. This is also why in my tests it happened to be always around 255 entries since I've always chosen timespans larger than 30 minutes.
Activity
metalmatze commentedon Jan 8, 2021
I don't think it's an intentional limitation. So definitely feel free to propose changes that would improve this!
Knuspel commentedon Jan 28, 2021
The limit of entries in this issue is due to the resolution of data in the "steps" functionality.
I'd propose to add a parameter in the CLI that allows the user to set the steps in seconds.
In prometheus.go once the selected timeframe goes over 30 Minutes the stepping is calculated by dividing the queried amount of minutes by 4.2. This leads to roughly the same amount of entries once you exceed a 30 minute threshold. This is also why in my tests it happened to be always around 255 entries since I've always chosen timespans larger than 30 minutes.