You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- `mode`- The metric used to scale your workload. It's the `PascalCase` of the official metric name. For example, if you are going to leverage the metric `subscription/pull_request_count`, you will fill the value as `PullRequestCount`. Please refer to https://cloud.google.com/monitoring/api/metrics_gcp#gcp-pubsub. All metrics starting with `subscription/` and `topic/` are supported. (Default: `SubscriptionSize`, aka `NumUndeliveredMessages`)
I'm wondering if you can document a recommendation for the value of stabilizationWindowSeconds given that the underlying pubsub metrics are sampled only every 60s and can take up to 120s to update.
Otherwise, this might unnecessarily scale to the max due to the rate at which the metric updates
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Oct 12, 2024
keda-docs/content/docs/2.14/scalers/gcp-pub-sub.md
Line 35 in c01eb79
I'm wondering if you can document a recommendation for the value of
stabilizationWindowSeconds
given that the underlying pubsub metrics are sampled only every 60s and can take up to 120s to update.Otherwise, this might unnecessarily scale to the max due to the rate at which the metric updates
The text was updated successfully, but these errors were encountered: