GCP pub/sub MQL no longer supported(recommend PromQL) - Starting October 22, 2024

[yazimpact]

Report

GCP Monitoring Page saw below warning:

Starting October 22, 2024, Monitoring Query Language (MQL) will no longer be a recommended query language for Cloud Monitoring, and we will begin to turn off certain usability features. We recommend moving to PromQL , the open-source standard for querying time series. PromQL offers similar functionality to MQL, with a wider user base and more community resources. Learn more

Expected Behavior

Use Promql instead of MQL

Actual Behavior

Current metrics is using MQL:

pubsub.googleapis.com/subscription/num_undelivered_messages
| filter (resource.project_id == 'project-name' && resource.subscription_id == 'example-sub')
| within 1m

Steps to Reproduce the Problem

References:
PROMQL:
https://cloud.google.com/monitoring/promql
MQL:
https://cloud.google.com/stackdriver/docs/deprecations/mql

Logs from KEDA operator

example

KEDA Version

2.13.1

Kubernetes Version

1.30

Platform

Google Cloud

Scaler Details

GCP Pub/Sub

Anything else?

https://cloud.google.com/stackdriver/docs/deprecations/mql

On October 22, 2024, Monitoring Query Language (MQL) will no longer be a recommended query language for Cloud Monitoring.

On October 22, 2024, certain usability features will be turned off.
On July 22, 2025, MQL will no longer be available for new dashboards and alerts in the Google Cloud console, and Google Cloud customer support will end. Existing MQL dashboards and alerts will continue to work, and you will still be able to create MQL dashboards and alerts using the Cloud Monitoring API.

[JorTurFer]

Interesting update 😄

@kedacore/keda-core-contributors , do you think that we should get rid of the GCP Scalers or just use them as wrapper on top of the prometheus one to make the things easier to end users?

[yazimpact]

@JorTurFer any updated? Keda started getting errors for scaling:

github.com/kedacore/keda/v2/pkg/scalers.(*pubsubScaler).GetMetricsAndActivity
        /workspace/pkg/scalers/gcp_pubsub_scaler.go:193
github.com/kedacore/keda/v2/pkg/scaling/cache.(*ScalersCache).GetMetricsAndActivityForScaler
        /workspace/pkg/scaling/cache/scalers_cache.go:140
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScalerState
        /workspace/pkg/scaling/scale_handler.go:743
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScaledObjectState.func1
        /workspace/pkg/scaling/scale_handler.go:628
2024-10-23T11:08:11Z    ERROR   scale_handler   error getting scale decision    {"scaledObject.Namespace": "example", "scaledObject.Name": "example-scaledobject", "scaler": "pubsubScaler", "error": "could not find stackdriver metric with query fetch pubsub_subscription | metric 'pubsub.googleapis.com/subscription/num_undelivered_messages' | filter (resource.project_id == 'project_name' && resource.subscription_id == 'example-sub') | within 1m"}
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScalerState
        /workspace/pkg/scaling/scale_handler.go:764
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScaledObjectState.func1
        /workspace/pkg/scaling/scale_handler.go:628

[wozniakjan]

am I reading https://cloud.google.com/stackdriver/docs/deprecations/mql correctly by expecting MQL to work until July 22, 2025?

also the same document mentions:

No action is required to continue using your existing MQL assets, and you can create new MQL assets by using the Cloud Monitoring API.

[yazimpact]

@wozniakjan @JorTurFer Will you update gcp scalers to use promql? or thinking to update in next keda versions?

[JorTurFer]

I'm not 100% sure about the right solution, let's talk about this during next standup @zroubalik @wozniakjan