Live Production Debugging with Cloud Foundry and Stackdriver in 3 Easy Steps
summary
Connects Cloud Foundry apps to the Stackdriver Debugger via the Java buildpack so debugging in prod only needs: a GCP project, cloud debugger user role, the CF GCP service broker, and a restage. Features are dynamic Stackdriver Debugger breakpoints (snapshots) and log points, snapshots include full call stacks, are shareable for 30 days, log history holds 24 hours, and the agent adds ~1–3% overhead. Example app (Reddit + Vision API) exposes a bug (used == instead of .equals); changing code and restaging fixes it.
AI-written summary · about
chapters (13)
- 0:00Introduction and motivation
- 1:07Stackdriver basics and setup
- 3:19Demo application overview
- 4:33Creating Stackdriver service
- 6:18Debugger UI and source setup
- 7:27Debug points and snapshots
- 12:51Log points and filtering
- 17:53Debugging the live issue
- 19:09Application versioning
- 20:22Sharing debug snapshots
- 21:32How it works and overhead
- 23:04Cloud agnostic and costs
- 23:46Resources and Q&A intro
related talks
57mDebugging Java in Production on Google Cloud Platform
25mMonitoring Cloud Foundry Infrastructure and Applications with Stackdriver and BigQuery
22mAnalyzing Pets and Live Debugging: Using Google's Machine Learning APIs and Stackdriver Debugger
31mRunning Java Applications on Cloud Foundry
30mCloud Native Debugging in Production - Dig Deep into your agents
33mDebugging & Profiling Spinnaker Applications Live!
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
25mDebugging at Scale in Production with kubectl debug