Debugging Cloud Applications Locally
A developer has a cloud application that behaves incorrectly.
Intermediate · Developer · Documented building blocks
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. Start with the linked book exercises, which document the existing building blocks.
What Quinzee contributes
You can inspect the client and local service boundaries on the same development machine.
The proposed example
Reproduce a failing service call, inspect endpoint resolution and TLS, then correlate the request with platform and application telemetry.
Required capabilities
Local diagnostic access and configured platform/application telemetry.
Boundaries and remaining work
Logs Query implements a bounded KQL subset. Platform diagnostics and application telemetry have separate stores and purposes.
What to verify
- Identify the first failing layer instead of disabling verification.
- Reduce the failure to one SDK call with a reproducible expected result.
Read the three perspectives
- The Book of Quinzee: Observe your application
- The Book of Quinzee: Troubleshoot a connection or workflow
- The Book of Quinzee: Debug your application and QHQ
- The Book of Quinzee: Deploy monitoring with the application
- Quinzee Administrator’s Guide: Observe the platform and the application separately · Primary reference
- Quinzee Administrator’s Guide: Diagnose failures from the outside inward · Primary reference
- Quinzee Internals: HTTP library and asynchronous execution
- Quinzee Internals: Connection and streaming lifecycle
- Quinzee Internals: Telemetry and Azure monitoring
- Quinzee Internals: Inspect a disposable instance from Linux