CSE46 · Cloud foundations
Observability Detective
Users say the site is slow. Use metrics, logs and traces together to find the slow service.
🎯 You will learn to
- Tell metrics, logs and traces apart
- Follow a trace ID
- Find the bottleneck
📘 Guided lab
This mission is a guided walkthrough: follow the steps on your own computer or practice account. The in-browser simulator for it is planned for a later release.
✅ Steps & checkpoints
🗺️ Metrics, logs, traces
Metrics show that latency rose, traces show which span is slow, and logs explain why.
The 2D diagram shows the exact flow, ports and trust boundaries. The 3D scene is a concept view of the same parts; packets travel along the same arrows.
🤔 Think about it
Why do you need a trace ID in every log line?
🛡️ Safety & cost
Mock cloud: no account, no resources, no cost.
🧹 Cleanup
Mock resources disappear when you leave the page.
📚 Reference documents
- OpenTelemetry documentation · OpenTelemetry
- Azure Monitor overview · Microsoft Learn
- What is Amazon CloudWatch? · AWS
- Azure Well-Architected Framework · Microsoft Learn
- AWS Well-Architected Framework · AWS
Official sources, checked on 5 Nov 2026. Cloud services change often; check the official page before relying on a feature. All references