End-to-end flows
These diagrams show how the containers cooperate to deliver a business outcome. They are the best starting point for a developer who needs to understand the runtime path rather than the deployment shape.
| Flow | Diagram | What it shows |
|---|---|---|
| Profiling session lifecycle | sequence |
How a threshold breach in the customer application becomes a trace file, an analysis, and a verified fix. |
| Trace file lifecycle | state |
The statuses a trace file moves through, from the profiler upload to the analyst's archive. |
| Diagnostic bot request | sequence |
How a Teams message becomes a control-plane read or an asynchronous diagnosis. |
| Collect Sync workflow | sequence |
The analyst-side CLI that turns assigned traces into local files and archives closed traces. |
| Production deployment topology | flowchart |
How the production workload is hosted and which managed services each app depends on. |
| Diagnostic bot installation | sequence |
The operator path for publishing the diagnostic bot to Teams. |
The flow index is generated from
architecture/model.yaml. Edit the model, not this page.