fix: Get current api usage InfluxDB query #3846
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
A month or two ago I wrote a function to get current API usage, but I was limited to testing with the developer and staging keys and the amount of records returned from the database seemed low, but still seemed reasonable given that organisations in staging could reasonably be argued to not have much API use.
While testing with real production data the difference in the returned results against what we already know should be the right result made it apparent that this function was malfunctioning. Looking at other queries in the InfluxDB wrapper module I was able to alter the function in order to produce the correct result.
How did you test this code?
Tested against production data and verified that the total API calls were an exact match.