Recommendations Next Steps

microsoft/sre-agent/labs/zava-learning/sre-config/agent-config/skills/recommendations-next-steps

analysisResmi

Resmi Sağlayıcı Skill'iView repo

Use to produce the forward-looking recommendations and next steps for a Zava Learning incident — prioritized preventive, detective, and process actions with owners, target dates, and the risk of inaction. Its output is used in the zava-reporting deliverables.

Dosyalar1 dosya

SKILL.md44 satır

Loading editor…

Kurulum

Önerilen

Tek komut — ajanınız otomatik olarak devreye alır.

AI aracını seç

Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.

veya

Manuel Kurulum

Daha fazla adım

Dosyayı indirin ve ajanınızın sistem istemine yapıştırın.

Skill detayları

Versiyonv1.0.0

YazarMicrosoft

Kategorianalysis

Skill IDmicrosoft/sre-agent/labs/zava-learning/sre-config/agent-config/skills/recommendations-next-steps

İlgili skill'ler

Azure Monitor RcaInvestigate Azure Monitor incidents using application, database, and network evidence without changing workload resources.Connectivity TriageUse 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.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. QueryLogAnalyticsByWorkspaceId Email Incident FollowupDraft an opted-in incident email and request approval before sending, with best-effort duplicate checks.