fix(function-autoscaler): use metric-specific environment labels - #857
Conversation
Signed-off-by: Bora Oztekin <boztekin@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughChangesMetric environment query updates
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The change updates autoscaler queries to use metric-specific environment labels; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
🛡️ CodeQL Analysis🚨 Found 2 issue(s) Severity Breakdown:
📋 Top Issues🔗 View full details in Security tab 🕐 Last updated: 2026-08-14 05:42:47 UTC | Commit: c384cb0 |
|
🎉 This PR is included in version nvcf-function-autoscaler-v1.20.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
TL;DR
Use the environment labels emitted by each autoscaler metric family:
aws_envfor invocation/control-plane utilization, workerenvironmentlabels for worker metrics, and control-planeenvironmentlabels for instance-only queries.Additional Details
state="active"matcher.For the Reviewer
Please focus on the query construction in
work/mod.rsandwork/discovery.rs.For QA
Issues
NO-REF
Checklist
Summary by CodeRabbit