Docs : add timeout parameter to Metrics API scaler#1720
Open
RokeshVS wants to merge 1 commit intokedacore:mainfrom
Open
Docs : add timeout parameter to Metrics API scaler#1720RokeshVS wants to merge 1 commit intokedacore:mainfrom
RokeshVS wants to merge 1 commit intokedacore:mainfrom
Conversation
Signed-off-by: rvijayakumar-rpx <rvijayakumar_c@rpxcorp.com>
✅ Deploy Preview for keda ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thank you for your contribution! 🙏 We will review your PR as soon as possible.
Learn more about:
|
rickbrouwer
approved these changes
Mar 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Documents the new
timeouttriggerMetadata parameter added to the Metrics API scaler.The
timeoutfield allows users to override the global KEDA HTTP client timeout on a per-trigger basis for the Metrics API scaler (value in milliseconds). If not set, the global HTTP timeout configured for KEDA is used. The value must be greater than0.This is consistent with the same parameter already documented for the Prometheus and Azure Log Analytics scalers.
Checklist
Fixes #7549
Relates to kedacore/keda#7551