hands-on lab

Find Application Performance Bottlenecks With Google Cloud Trace

Difficulty: Intermediate

Duration: Up to 40 minutes

Students: 245

Rating: 5/5

Start lab

On average, students complete this lab in25m

Get guided in a real environmentPractice with a step-by-step scenario in a real, provisioned environment.

Learn and validateUse validations to check your solutions every step of the way.

See resultsTrack your knowledge and monitor your progress.

About

Author

Description

In this lab, you will be instrumenting a Java Spring Application that you will create in a Compute Engine IDE. The application has a couple of APIs. One contains a long-running operation creating a performance bottleneck. There are a few Google Cloud Services that can help you to monitor the application performance. This lab is the first in a series of two and focuses on Cloud Trace.

Application performance should be regularly optimized to minimize latency issues. Users often find it difficult to monitor the performance or latency issues. Google Cloud provides a suite of tools to help you overcome application performance management issues. These tools provide insights into how your code performs and enable you to take proactive actions to resolve any issues. You will investigate the following tools in the context of the sample Java application to understand how they work first-hand in a series of labs:

Cloud Trace helps you analyze the latency of applications. It shows a summarised view of the APIs and the time taken to execute in near real-time.
Cloud Profiler helps you analyze performance issues, CPU utilization, and memory usage. It helps your application to perform better by optimizing intensive function calls and code.
Cloud Debugger (now deprecated) helps you debug your production code by loading the production code in Google Cloud. As a developer, there are certain times when you notice issues in production. To debug the issues without taking the application offline or disturbing impacting latency, you can use Cloud Debugger.