devopsOfficial
Official Provider SkillView repo
Use for any Zava Learning incident where students cannot reach the platform or actions fail at the network/edge layer — quiz launches failing, portal 5xx, requests timing out, or backends appearing unhealthy. Traces the full request path (Application Gateway -> NSG -> Container Apps internal load balancer -> APIs) from telemetry and Azure config, finds the broken hop, and remediates within the permitted-action boundary.
Files1 files
SKILL.md73 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the file and paste it into your agent's system prompt.
Skill details
Versionv1.0.0
AuthorMicrosoft
Categorydevops
Skill IDmicrosoft/sre-agent/labs/zava-learning/sre-config/agent-config/skills/connectivity-triage
Related skills
Azure Monitor RcaInvestigate Azure Monitor incidents using application, database, and network evidence without changing workload resources.Cost AnalysisUse when an operator or a scheduled task requests a periodic cloud-cost / spend audit of the Zava Learning resource group — identify the top cost drivers, week-over-week trend, idle or oversized resources, and concrete savings opportunities. Read-only; produces findings for a report.Deploying DemoDeploy the SRE Agent demo end-to-end. Use when asked to set up, deploy, or get this demo running.Deployment Compliance CheckChecks whether Azure Container App deployments comply with the organization's CI/CD-only deployment policy. Uses three signals: Activity Log caller identity, Docker image labels (tamper-proof), and resource tags.
QueryLogAnalyticsByWorkspaceIdEmail Incident FollowupDraft an opted-in incident email and request approval before sending, with best-effort duplicate checks.Evidence Before AfterUse to build the before-and-after visual evidence for a Zava Learning incident. First classify the fault, then render the ONE visual that actually explains what changed — a before/after path or topology diagram for connectivity/config/RBAC faults, or time-series comparison charts for performance/availability faults — plus a state/metric delta table. Never plot a metric that does not tell the story. Its output is used in the RCA and the zava-reporting deliverables.