Assigned
Status Update
No update yet.
Comments
pu...@google.com
je...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
The consolidation lag in the monitoring api to get the count of unread messages on a pub/sub subscription/topic makes it unusable for real time scenarios.
What you expected to happen:
When a message hits the topic/subscription, i should be able to call an api method that gives me the live count of unread messages.
While I could do a pull and count the messages that way, for 100,000 messages, that's unfeasible for many reasons.
Considering the fact that there is a Google Monitoring Metric for num_outstanding_messages which is sampled every 60 seconds, there should already be a method that exists to get the count, so just expose that method to the public directly.
This feature is important for queue based scaling technologies such as KEDA which rely on triggers to take an action.
If KEDA can directly count the number of messages on the queue, it can trigger a scaling event accordingly.