https://cloud.google.com/run/docs/monitoring#custom-metrics
https://cloud.google.com/run/docs/monitoring#add_alerts
https://cloud.google.com/monitoring/alerts

https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup- probes/#define-startup-probes The kubelet uses startup probes to know when a container application has started. If such a probe is configured, it disables liveness and readiness checks until it succeeds, making sure those probes don't interfere with the application startup. This can be used to adopt liveness checks on slow starting containers, avoiding them getting killed by the kubelet before they are up and running.

https://cloud.google.com/blog/products/containers-kubernetes/ensuring-reliability-and-uptime-for- your-gke-cluster Setting PodDisruptionBudget ensures that your workloads have a sufficient number of replicas, even during maintenance. Using the PDB, you can define a number (or percentage) of pods that can be terminated, even if terminating them brings the current replica count below the desired value. With PDB configured, Kubernetes will drain a node following the configured disruption schedule. New pods will be deployed on other available nodes. This approach ensures Kubernetes schedules workloads in an optimal way while controlling the disruption based on the PDB configuration.

https://cloud.google.com/storage/docs/access-control/signed-urls#should-you-use In some scenarios, you might not want to require your users to have a Google account in order to access Cloud Storage, but you still want to control access using your application-specific logic.
The typical way to address this use case is to provide a signed URL to a user, which gives the user read, write, or delete access to that resource for a limited time. You specify an expiration time when you create the signed URL. Anyone who knows the URL can access the resource until the expiration time for the URL is reached or the key used to sign the URL is rotated.

https://cloud.google.com/appengine/docs/standard/python/application-security The Google Cloud Web Security Scanner discovers vulnerabilities by crawling your App Engine app, following all that links within the scope of your starting URLs, and attempting to exercise as many user inputs and event handlers as possible.
https://cloud.google.com/security-command-center/docs/concepts-web-security-scanner-overview Web Security Scanner custom scans provide granular information about application vulnerability findings, like outdated libraries, cross-site scripting, or use of mixed content.