The Google Cloud Operations suite (formerly Stackdriver) includes a wide variety of tools to help you monitor and debug your GCP-hosted applications. This course will give you hands-on demonstrations of how to use the Monitoring, Logging, Error Reporting, Trace, and Profiler components of the Cloud Operations suite. You can follow along with your own GCP account to try these examples yourself.
If you have any feedback relating to this course, feel free to reach out to us at email@example.com.
- Use the Cloud Operations suite to monitor, log, report on errors, trace, and profile
- System administrators
- People who are preparing to take the Google Associate Cloud Engineer certification exam
- Overview of Google Cloud Platform course or experience with Google Cloud Platform
- The GitHub repository for this course is at https://github.com/cloudacademy/google-cloud-ops.
I hope you enjoyed learning about the Cloud Operations Suite. Let’s do a quick review of what you learned.
You can use the Cloud Operations suite (formerly known as Stackdriver) for monitoring, logging, error reporting, profiling, and tracing your applications.
You don’t need to install the Ops Agent on a virtual machine instance to be able to use Monitoring, but if you do install it, you can get more information about the instance, such as about the third-party software running on it.
To monitor a server’s availability, first, you need to create an Uptime Check. Then you need to set up an Alert Policy. To create your own custom set of graphs, create a Dashboard.
Cloud Audit Logs keep track of who did what, where, and when. There are four types of audit logs. Admin Activity logs track any actions that modify a resource. This includes everything from shutting down VMs to modifying permissions. System Event logs track Google Cloud’s actions on resources. Some examples are maintenance of an underlying virtual machine host and reclaiming a spot VM. Data Access logs track data requests, including read requests on configurations and metadata.
If you want to send logs from a virtual machine’s guest operating system to Cloud Logging, then you’ll need to install the Ops Agent on the VM.
If you need to do serious log analysis, then you can export the logs to BigQuery. In this case, BigQuery acts as a sink for log data. To do a search in BigQuery, you need to use SQL statements.
The Error Reporting service alerts you to errors in your applications.
Cloud Profiler and Cloud Trace are used to analyze performance problems in applications. A trace is an individual request to an application. Cloud Trace shows you how much time was taken by each of the calls generated by an application request.
If you’re running your applications in App Engine, then it’ll automatically capture and submit traces. If you want to trace code that’s running outside of App Engine, then you’ll have to add instrumentation code to your applications. The recommended way is to use the OpenTelemetry library.
That’s it for this introduction to Google Cloud Operations Suite. Please give this course a rating, and if you have any questions or comments, please let us know. Thanks!
Guy launched his first training website in 1995 and he's been helping people learn IT technologies ever since. He has been a sysadmin, instructor, sales engineer, IT manager, and entrepreneur. In his most recent venture, he founded and led a cloud-based training infrastructure company that provided virtual labs for some of the largest software vendors in the world. Guy’s passion is making complex technology easy to understand. His activities outside of work have included riding an elephant and skydiving (although not at the same time).