At the moment we visually have a way of seeing how many queries out of our total allocation until the end of the month we have used.
What we can’t see without some basic maths is whether if we continue using the same approximate queries per day, whether we’re going to be over at the end of the time period or not.
Having this data would be useful to determine whether changes need to be made to prevent the cap being hit whether it be due to issues on the users network, or planning whether an upgrade will be needed.
Proposed solution
The solution I’d incorporate is showing a visual overlay over the top of the requests progress bar to show where usage would be if kept linearly on track over the month.
See below for example.
Requests
Requests Per Month
10,000,000
Requests to Day Average
1,428,571
Current Requests
500,321
Remaining
9,499,679
Equation used was Requests Per Month/(MONTH(TODAY())-1)
As an addition, an indicator could also be shown as to where the users average requests at that time usually are at that time of the month.
Issue Details
At the moment we visually have a way of seeing how many queries out of our total allocation until the end of the month we have used. What we can’t see without some basic maths is whether if we continue using the same approximate queries per day, whether we’re going to be over at the end of the time period or not.
Having this data would be useful to determine whether changes need to be made to prevent the cap being hit whether it be due to issues on the users network, or planning whether an upgrade will be needed.
Proposed solution
The solution I’d incorporate is showing a visual overlay over the top of the requests progress bar to show where usage would be if kept linearly on track over the month.
See below for example.
Equation used was
Requests Per Month/(MONTH(TODAY())-1)
As an addition, an indicator could also be shown as to where the users average requests at that time usually are at that time of the month.
Alternative solution
No response