-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement rate limiting and backoff for UptimeRobot #358
Labels
Comments
karl-johan-grahn
added
kind/enhancement
New feature or request
kind/help wanted
Extra attention is needed
labels
Mar 15, 2023
This issue is stale because it has been open for 60 days with no activity. |
not stale please |
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Reopening issues that inadvertently were closed as stale |
This issue is stale because it has been open for 60 days with no activity. |
not stale please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Similar to #106, it would be nice if controller could have a max req per minute setting and could respect a retry-After header, to avoid printing a lot of 429 errors for free UptimeRobot accounts.
The text was updated successfully, but these errors were encountered: