Skip to content

docs: Add Azure Cosmos DB Change Feed scaler documentation#1721

Open
yash2710 wants to merge 5 commits intokedacore:mainfrom
yash2710:feat/azure-cosmosdb-scaler-docs
Open

docs: Add Azure Cosmos DB Change Feed scaler documentation#1721
yash2710 wants to merge 5 commits intokedacore:mainfrom
yash2710:feat/azure-cosmosdb-scaler-docs

Conversation

@yash2710
Copy link
Copy Markdown

@yash2710 yash2710 commented Mar 17, 2026

Add scaler documentation for the new azure-cosmosdb trigger type. Covers connection string and workload identity auth, .NET/Java SDK lease format compatibility, and complete ScaledObject examples.

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO)

Relates to kedacore/keda#7556, kedacore/keda#7557

Add scaler documentation for the new azure-cosmosdb trigger type.
Covers connection string and workload identity auth, .NET/Java SDK
lease format compatibility, and complete ScaledObject examples.

Signed-off-by: Yash Trivedi <yash2710@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yash2710 yash2710 requested a review from a team as a code owner March 17, 2026 19:23
@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 17, 2026

Deploy Preview for keda ready!

Name Link
🔨 Latest commit 31778ff
🔍 Latest deploy log https://app.netlify.com/projects/keda/deploys/69cc1d3bffb07200085a4bc5
😎 Deploy Preview https://deploy-preview-1721--keda.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions
Copy link
Copy Markdown

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

  • Add your contribution to all applicable KEDA versions
  • GitHub checks are passing
  • Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

Update parameter names and descriptions to reflect the total-lag-based
scaling approach (matching EventHub scaler pattern):
- lagThreshold -> changeFeedLagThreshold (default: 100)
- activationLagThreshold -> activationChangeFeedLagThreshold
- Metric is now total estimated lag, not partition count

Signed-off-by: Yash Trivedi <yash2710@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yash2710 yash2710 marked this pull request as ready for review March 19, 2026 20:38
yash2710 and others added 3 commits March 24, 2026 13:52
Document the scale-to-max-on-error behavior including cached and
uncached partition count fallback paths.

Signed-off-by: Yash Trivedi <yash2710@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
When no cached partition count is available, the scaler returns an error
to KEDA instead of a large fallback value. Users should configure
fallback on the ScaledObject for explicit failure behavior.

Signed-off-by: Yash Trivedi <yash2710@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Clarify that processorName is used to filter lease documents by ID
prefix, enabling accurate lag estimation when multiple processors
share a lease container.

Signed-off-by: Yash Trivedi <yash2710@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant