AI-Assisted Cloud Debugging
An application fails during execution.
Intermediate · Developer · Tooling planned
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. The proposed workflow still needs end-to-end implementation and verification.
What Quinzee contributes
Local diagnostics can supply evidence for hypotheses rather than relying on generated explanations alone.
The proposed example
Prepare a minimal failure and a redacted set of request metadata, configuration and diagnostics for assistant-supported investigation.
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
- Exclude secrets and customer payloads from the assistant context.
- Verify the proposed explanation by reproducing and fixing the failing request.
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