Set a meaningful Cloud Run request floor
When configuring a Cloud Monitoring signal to count service traffic, use a metric that counts all requests. A narrow filter can make busy windows appear too quiet to compare.
Check the metric, labels and statistic#
A traffic floor compares the signal's total in each window, so the signal must count every request of the service: a Sum per second of a request total, such as run.googleapis.com/request_count with no response-code label on Cloud Run. A signal filtered to errors, such as one with response_code_class=5xx, counts only the errors. A Data points per second of run.googleapis.com/request_count counts one point a minute for each series, however many requests each point records. Either can count fewer than the floor while the service is busy.