Book Image

Building Google Cloud Platform Solutions

By : Ted Hunter, Steven Porter, Legorie Rajan PS
Book Image

Building Google Cloud Platform Solutions

By: Ted Hunter, Steven Porter, Legorie Rajan PS

Overview of this book

GCP is a cloud computing platform with a wide range of products and services that enable you to build and deploy cloud-hosted applications. This Learning Path will guide you in using GCP and designing, deploying, and managing applications on Google Cloud. You will get started by learning how to use App Engine to access Google's scalable hosting and build software that runs on this framework. With the help of Google Compute Engine, you’ll be able to host your workload on virtual machine instances. The later chapters will help you to explore ways to implement authentication and security, Cloud APIs, and command-line and deployment management. As you hone your skills, you’ll understand how to integrate your new applications with various data solutions on GCP, including Cloud SQL, Bigtable, and Cloud Storage. Following this, the book will teach you how to streamline your workflow with tools, including Source Repositories, Container Builder, and Stackdriver. You'll also understand how to deploy and debug services with IntelliJ, implement continuous delivery pipelines, and configure robust monitoring and alerts for your production systems. By the end of this Learning Path, you'll be well versed with GCP’s development tools and be able to develop, deploy, and manage highly scalable and reliable applications. This Learning Path includes content from the following Packt products: • Google Cloud Platform for Developers Ted Hunter and Steven Porter • Google Cloud Platform Cookbook by Legorie Rajan PS
Table of Contents (29 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Monitoring and alerting


Logging and tracing provide a wealth of information about how components of your cloud systems are behaving, but they generally only provide a partial picture of system behavior as a whole. Many important aspects of system health exist outside the scope of logging and tracing. Very often these aspects are best measured in terms of change over time, allowing developers to identify trends and anomalies.

Building on our to-do example, a sudden spike in concurrent connections to our todos-db Cloud SQL instance may indicate that a recently pushed version of todos-backend is not correctly terminating stale connections. Likewise, identifying patterns in user traffic to our todos-frontend may allow us to identify optimal maintenance windows or eagerly scale ahead of demand.

Additionally, while collecting the right data is important to effectively monitor cloud systems and triage issues, it does not provide developers with the early awareness of issues required to minimize downtime...