-
Notifications
You must be signed in to change notification settings - Fork 13
monitoring: add buildkit autoscaling alerts #727
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
Open
huydhn
wants to merge
8
commits into
gh/huydhn/37/base
Choose a base branch
from
gh/huydhn/37/head
base: gh/huydhn/37/base
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+53
−1
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
51 changes: 51 additions & 0 deletions
51
osdc/modules/monitoring/kubernetes/alerts/buildkit-autoscaling-alerts.yaml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,51 @@ | ||
| apiVersion: monitoring.coreos.com/v1 | ||
| kind: PrometheusRule | ||
| metadata: | ||
| name: buildkit-autoscaling-alerts | ||
| namespace: monitoring | ||
| labels: | ||
| app.kubernetes.io/part-of: osdc-monitoring | ||
| spec: | ||
| groups: | ||
| - name: buildkit-autoscaling | ||
| rules: | ||
| # KEDA can't read the scale metric — if it persists past the ScaledObject's | ||
| # failureThreshold, KEDA drops to the fixed fallback pool instead of scaling. | ||
| - alert: BuildkitKedaScalerErrors | ||
| expr: | | ||
| sum by (scaledObject) (increase(keda_scaler_detail_errors_total[15m])) > 0 | ||
| for: 10m | ||
| labels: | ||
| severity: warning | ||
| team: pytorch-dev-infra | ||
| priority: P3 | ||
| annotations: | ||
| summary: "KEDA can't read the scale metric for {{ $labels.scaledObject }}" | ||
| description: "KEDA scaler errors for {{ $labels.scaledObject }} over the last 15m; sustained errors trip the fallback to the fixed BuildKit pool." | ||
|
|
||
| - alert: BuildkitKedaScaledObjectErrors | ||
| expr: | | ||
| sum by (scaledObject) (increase(keda_scaled_object_errors_total[15m])) > 0 | ||
| for: 10m | ||
| labels: | ||
| severity: warning | ||
| team: pytorch-dev-infra | ||
| priority: P3 | ||
| annotations: | ||
| summary: "KEDA ScaledObject {{ $labels.scaledObject }} reconcile errors" | ||
| description: "KEDA failed to reconcile ScaledObject {{ $labels.scaledObject }} in the last 15m; autoscaling for that arch may be stale." | ||
|
|
||
| # A real backlog the pool can't keep up with. The >20 threshold (not >0) | ||
| # avoids firing on normal burst churn, where small batches keep the queue | ||
| # briefly non-zero but still drain within minutes as pods scale up. | ||
| - alert: BuildkitQueueBacklog | ||
| expr: | | ||
| haproxy_backend_current_queue{proxy=~"bk_amd64|bk_arm64"} > 20 | ||
| for: 15m | ||
| labels: | ||
| severity: warning | ||
| team: pytorch-dev-infra | ||
| priority: P3 | ||
| annotations: | ||
| summary: "BuildKit {{ $labels.proxy }} backlog: >20 builds queued for 15m" | ||
| description: "More than 20 builds have been waiting in the {{ $labels.proxy }} queue for 15m — beyond normal burst churn; the pool isn't scaling up fast enough (or is at max)." | ||
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect that during peak this one will mis fire, say batches of 2 arrive at minute 0, 3, 10, 14.
This will fire, even they are all scaling in 7-8 minutes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should
haproxy_backend_current_queue{proxy=~"bk_amd64|bk_arm64"} > 20or other valueThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done — bumped it to
> 20. With the 15m window that won't fire on normal burst churn (your 0/3/10/14 example stays well under 20 and drains in minutes); it only trips on a real sustained backlog the pool isn't clearing.