Inaccurate saturation query for max concurrent requests
What
Previously, instances were limited to 1. When introducing autoscaling, existing query for Max Concurrent Requests resource appears to show saturation on service overview dashboard:
However, it does not reflect the Cloud Run dashboard:
Update the runway_container_max_concurrent_requests
query to accurately reflect Cloud Run console.
Why
For https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1301.
Edited by Chance Feick