Skip to content
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

[Azure Pipelines Scalar] Create log entry when Azure DevOps API rate limit is (nearly) reached #6284

Open
raherrebrugh opened this issue Oct 30, 2024 · 0 comments · May be fixed by #6285
Open
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@raherrebrugh
Copy link

Proposal

I want the keda operator to create a log warning when the Azure Pipelines Scalar makes a call to Azure DevOps API and the response indicates the API rate limit is (nearly) reached.

Azure DevOps API sets the following (among other) headers when the API rate limit is (nearly) reached:

  1. X-RateLimit-Delay
  2. X-RateLimit-Remaining

X-RateLimit-Delay indicates by how many seconds the requests are delayed
X-RateLimit-Remaining indicates how many TSTUs are left before request are being rate limited

More information on the headers is documented at
https://github.com/MicrosoftDocs/azure-devops-docs/blob/main/docs/integrate/concepts/rate-limits.md

Use-Case

I would like to be able to monitor the logs and detect when the account used by Keda is reaching the Azure DevOps API Rate Limits. This allows me to detect a potential issue before the entire queueing mechanism freezes up because Keda is overloading the Azure DevOps API.

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

@raherrebrugh raherrebrugh added feature-request All issues for new features that have not been committed to needs-discussion labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Status: To Triage
Development

Successfully merging a pull request may close this issue.

1 participant