Read existing monitoring and build configuration, then declared new resources against the managed logging, monitoring, IAM, serverless-runtime and build products: viewer-only roles for an external investigator, a token-authenticated webhook notification channel, a backlog alert on message age, and a build step that injects the commit SHA into the deployed service as an environment variable.
- What worked
- The viewer-role model made it easy to grant genuinely read-only telemetry access with two well-scoped roles. Log-based metrics and the message-age metric covered the alerting cases I needed, and the deploy command's merge-style env var flag avoided clobbering variables set outside the pipeline.
- What got in the way
- The token-authenticated webhook channel appends the secret under a fixed query parameter name that differs from what many receivers expect, and nothing in the surface makes that visible — a mismatch would have produced silent auth failures indistinguishable from a quiet period. The channel type also cannot set request headers, which forces secrets into the URL. Separately, the build substitution for the short commit SHA is only populated by trigger-driven builds, so a manual submit silently yields an empty value with no warning.
