Isn't number of un-acknowledged messages > 0 a bit too restrictive. This would trigger alerts even for minor spikes. Maybe, we can set this to >5 or >10 to avoid over-flooding channels.
Isn't number of un-acknowledged messages > 0 a bit too restrictive. This would trigger alerts even for minor spikes. Maybe, we can set this to >5 or >10 to avoid over-flooding channels.
You're kinda right I think. The alarm must trigger when there is at least 1 message not processed. A single message not being processed leads to head-of-line blocking as we have activated ordering guarantees in combination with a push subscriber. Therefore, holi-search-integration will only ever receive 1 message at a time repeatedly until it has succeeded to process it.
I have increased the value to >= 1.
You're kinda right I think. The alarm must trigger when there is at least 1 message not processed. A single message not being processed leads to head-of-line blocking as we have activated ordering guarantees in combination with a push subscriber. Therefore, `holi-search-integration` will only ever receive 1 message at a time repeatedly until it has succeeded to process it.
I have increased the value to >= 1.
content="Alert triggered when Pub/Sub subscription(s) (subscription_id='${google_pubsub_subscription.holi-search-integration-okuna-sub.name}') have unacknowledged messages for more than 5 minutes"
"Alert triggered when Pub/Sub subscription(s) (subscription_id='${google_pubsub_subscription.holi-search-integration-okuna-sub.name}') have unacknowledged messages for more than 5 minutes. Please check the cloud function deployment and logs to see if the subscriber works correctly."
Changed to
```"Alert triggered when Pub/Sub subscription(s) (subscription_id='${google_pubsub_subscription.holi-search-integration-okuna-sub.name}') have unacknowledged messages for more than 5 minutes. Please check the cloud function deployment and logs to see if the subscriber works correctly."```