Continuous feedback
What it is
Continuous feedback is the practice of automatically collecting telemetry and signals from production (usage, performance, errors, user behavior) and feeding them back to the team so decisions about the next iteration are data-driven. It’s the final “O” in the DevOps loop: Operate → Observe → learn → repeat.
Why it exists
Shipping is not the end. Without feedback, teams can’t know if a release helped, broke something, or was adopted. Feedback closes the loop and drives the next plan.
Key ideas
- Sources — application telemetry (telemetry), infrastructure metrics, logs (azure-monitor/log-analytics), user analytics (user-analytics), synthetic tests, alerts.
- Bidirectional — feedback flows back into planning/backlog (via azure-boards/GitHub issues) and into code (feature toggles, A/B).
- Dashboards & Workbooks surface the signal; alerts react to it.
Exam notes
- The AZ-400 Implement continuous feedback learning path: telemetry, usage analysis, and feedback loops into planning.
- See the full path note at continuous-feedback (the dedicated path). This is the cross-cutting concept.
Related
continuous-feedback · azure-monitor · telemetry · delivery-pipeline
📘 Source: Microsoft Learn — Feedback