Introduction to Continuous Feedback
Overview
Why “implement continuous feedback” is a core loop in the DevOps lifecycle. Releases don’t end when code ships — they start the observe → learn → plan cycle that makes the next release better.
Units
- Why continuous feedback matters
- What feedback is collected and acted on
- The tools that enable the loop
- How feedback feeds planning and delivery
Concepts introduced
- continuous-feedback — the practice of collecting and acting on production signals.
- feedback-loop — the cycle that turns data into the next planned work.
- telemetry — the raw signals (metrics, logs, traces) feeding the loop.
- azure-monitor and application-insights ground the loop in real Azure tooling.
Key terms & commands
- Monitoring vs feedback — monitoring observes; feedback changes what you build next.
- Tools map: Azure Monitor (infrastructure), Application Insights (application), Azure Boards (work items from insights).
Hands-on
- Identify which telemetry (infra vs app) to collect for a sample scenario.
- Sketch a feedback loop: collection → analysis → backlog → delivery.
Exam focus
- Know the two feedback dimensions: application/system and user/behavior.
- Recognize that telemetry/insights must feed the backlog (a loop), not just be displayed.