Challenge 06

Monitor the deployed app with the Azure SRE Agent

Use an authorized, non-production Azure environment.

Goal#

Use agents to monitor the deployed Octocat Supply application and improve its reliability, leveraging the Azure SRE Agent. Now that the app is deployed, the team wants agentic monitoring — detect, diagnose, and help remediate issues.

This challenge requires a reachable deployment from Challenge 5 in your own Azure subscription. Complete and verify that deployment before continuing; no shared reference environment is supplied.

Use only your disposable workshop deployment. Confirm the fault, rollback, permissions, and spending limit before testing; coordinate with any collaborators. Never inject faults into production or someone else's environment.

Actions#

  • Enable observability — Confirm the deployed app emits the telemetry needed for monitoring (logs, metrics, health checks). Add health/readiness endpoints if it doesn't already expose them.
  • Set up the SRE Agent — Connect the Azure SRE Agent to the deployed resources so it can observe application health.
  • Simulate an issue — Introduce or trigger a fault (e.g. a failing dependency or a bad deploy) that clearly affects health.
  • Investigate with the agent — Use the SRE Agent to identify root cause and suggest remediation.
  • Remediate — Apply the fix and confirm the agent reports healthy status.

Success criteria#

Capture what the agent surfaced vs. what you had to investigate manually, and note reliability improvements to feed back into the backlog.

Learning resources#

A prompt to start with

Adapt this to your chosen API track and actual environment. It starts a conversation; it does not complete the challenge for you.

Help me plan a controlled reliability exercise for my authorized, non-production deployment. Confirm telemetry, SRE permissions, the fault, rollback, and spending limit before making any change. Capture what the agent diagnoses versus what I investigate manually.

Ready for the next step?

Demonstrate each success criterion above and check it off. Completion is your assessment, not an automated test of your code.

Check all 4 success criteria before marking complete.

View this page's MarkdownLearning content is pinned to the credited upstream import.

Search the workshop

Solutions are not included.

    Search runs in your browser against the guide. It does not query GitHub or an AI service.

    Reset your workshop progress?

    This removes saved success criteria, completion marks, and the resume location in this browser. It does not change your repository or Azure resources.