| metadata | {"api_version":"azuresre.ai/v2","kind":"Skill"} |
| name | evidence-before-after |
| description | Use 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. |
| tools | ["RunAzCliReadCommands","GetAzCliHelp","ListAvailableMetrics","GetMetricTimeSeriesElementsForAzureResource","QueryAppInsightsByResourceId","QueryLogAnalyticsByResourceId","PlotBarChart","PlotAreaChartWithCorrelation","PlotScatter","ExecutePythonCode","SearchMemory"] |
Zava Learning — Before / After Evidence
Prove impact and recovery with the right visual for the fault — not a chart by reflex. Resource
Group: @@RG@@. Services: learner-portal, course-api, assessment-api. Retrieve zava-brand
and zava-report-template with SearchMemory and apply the house style. Use the windows and
root cause confirmed by rca-analysis.
Step 1 — Decide the visual FIRST (do not skip)
Classify what actually changed, then pick the visual that explains that. Plotting a smooth metric
for a binary/config fault (e.g. "availability before/after" for an NSG block) is misleading and
adds no insight — don't do it.
