Add a Cloud Monitoring signal for deploy verification

Choose a metric and the resource labels that identify your service. Proofline compares the selected series around deploys in the environment.

Choose the project and comparison#

Deploy verification compares the Cloud Monitoring metrics an environment watches before and after a deploy lands. Until the environment watches at least one signal, every deploy's checks end incomplete and the Inbox lists Choose signals. Only people who manage environments add signals.

  1. Open the environment's Setup → Deploy verification page.
  2. Under Signals, select Add signal.
  3. Enter the signal's Name.
  4. Check that Provider is Google Cloud Monitoring. The form starts there unless the environment has an AWS account and no Google Cloud project.
  5. Choose the Project the metric belongs to. The list offers each Google Cloud project that one of the environment's connections names. Only a Cloud Build connection reads Cloud Monitoring, and only once Verify capabilities has passed. The list marks a project with no such connection as cannot read metrics, and the signal cannot be saved there. Select Connect Google Cloud below the field, add a Cloud Build connection for the project, verify it, then return.
  6. Enter the Resource type and Metric type, such as cloud_run_revision and run.googleapis.com/request_count.
  7. Under Resource labels and Metric labels, enter one key=value per line to select the series, such as service_name=checkout and response_code_class=5xx. The project sets the project_id resource label.
  8. Under Comparison, set Statistic, Worse when, Tolerance (%) and Minimum change for that metric.
  9. For a signal that counts the service's requests with Sum per second or Data points per second, you may select Counts the service's requests and set Traffic floor (requests per window), 100 unless changed. Read a deploy's verification explains what a floor does.
  10. Select Add signal.

If the form shows Connect Google Cloud in place of Project, the environment has no Google Cloud project to read Cloud Monitoring from, and the signal cannot be saved. Select it to open the environment's Google Cloud page, add a Cloud Build connection for the project, verify its capabilities, then return.

Search help

Tab to a result. Enter to open. Escape to close.