Prevent rate limiting by StatusCake #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To prevent rate limiting with StatusCake two new things have been introduced. First of all, we cache the results of the GetAll function, so that it does not have to retrieve the status monitors everytime. Secondly, I added a latency after adding a monitor. Because even when the results are cached, if several monitors have to be added in a row, it will be invalidated and still hit the rate limit.
robinderooij-rl
force-pushed
the
statuscake-find-by-name-check
branch
from
c4c5e6b to
c8e5a2a
Compare
matthijswolters-rl
approved these changes
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To prevent rate limiting with StatusCake two new things have been introduced. First of all, we cache the results of the GetAll function, so that it does not have to retrieve the status monitors every time.
Secondly, I added a latency after adding a monitor. Because even when the results are cached, if several monitors have to be added in a row, it will be invalidated and still hit the rate limit.