Repository navigation
Add onprem-lab-http - #400
Merged
Merged
Conversation
Dalibor Kovacevic (RobiladK)
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a demo lab for an on-premises operations scenario: investigate an application outage on a local Ubuntu VM connected to Azure Arc, using telemetry collected in Azure.
What’s included
• A fault-injectable ASP.NET Core app and load generator running in Docker on the VM.
• Scripts and instructions to set up the host, connect it to Azure Arc, deploy monitoring, and inject or reset faults.
• KQL queries and a walkthrough for using Azure SRE Agent to investigate the simulated outage from application logs, host metrics, and Syslog.
The demo illustrates how Azure-based monitoring and SRE Agent can help troubleshoot workloads running outside Azure. The upstream dependency failure is simulated; it does not represent a real dependency outage.