Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Azure Chaos Studio Scenario reports record what happened during each Scenario run in Chaos Studio Workspaces: Action status, duration, affected resources, and overall run status. View or download a report to document your resilience test, then pair it with application monitoring to assess recovery. A successful run alone doesn't prove that your application recovered.
Important
Chaos Studio Workspaces and Scenarios are in public preview. Microsoft provides this preview "as is" and "as available," and it isn't covered by service-level agreements or limited warranty. Microsoft provides customer support for the preview on a best-effort basis. This preview isn't meant for production use. For more information, see the following articles:
Scenario reports serve three purposes:
- Operational evidence: After a resilience test, you have a concrete artifact showing what was tested, against which resources, and what the outcome was. Pair the report with your own application health checks and monitoring data to assess whether the system recovered within your target recovery time objective (RTO).
- Compliance documentation: Regulatory frameworks like DORA and industry standards for operational resilience increasingly require evidence that organizations test their systems against failure. Scenario reports provide that evidence in a structured, auditable format.
- Post-incident retrospectives: When you reproduce an outage pattern after an incident, the Scenario report documents whether the fix you applied improved resilience.
Report structure
A Scenario report contains four sections.
Run details
The top of the report shows metadata about the Scenario run:
| Field | Description |
|---|---|
| Scenario | The name and version of the Scenario that ran (for example, "ZoneDown-1.0"). |
| Configuration | The configuration profile used, if the Scenario supports multiple configurations. Defaults to "default." |
| Workspace | The name of the Workspace that owns this Scenario. |
| Run ID | A unique identifier (GUID) for this specific execution. Use this ID when referencing a run in support requests or automation. |
| Status | The overall outcome: Succeeded, Failed, or Canceled. |
| Started At | The timestamp when execution began. |
| Completed At | The timestamp when all actions finished or the run was canceled. |
Action summary
The action summary is a table listing every Action in the Scenario. Each row includes:
| Column | Description |
|---|---|
| Action | The internal name of the Action (for example, vmssZoneDown). |
| Display Name | A human-readable description of what the Action does (for example, "Force shutdown Virtual Machine Scale Set instances in target zone"). |
| Status | Succeeded: The Action executed and completed normally. Skipped: The Action didn't execute, usually because the target resource wasn't found in the Workspace scope or the Action's preconditions weren't met. Failed: The Action encountered an error during execution. |
| Duration | How long the action ran, from start to completion. |
| Started At / Completed At | Timestamps for the individual action. |
| Resources Targeted | The specific Azure resources the Action ran against. |
| Parameters | The configuration parameters passed to the Action (for example, zones: 3 for a zone-scoped shutdown, or RebootType: PrimaryNode for a Redis failover). |
Actions with a Skipped status are normal in many Scenarios. A Zone Down Scenario, for example, might include Actions for resource types that exist in the Scenario definition but aren't present in your Workspace scope. Skipped Actions don't affect the overall run status.
Important
If a Skipped action targets a resource type you expected to be in scope, investigate before treating the run as a valid resilience test. A common cause is a scope that doesn't include the expected resource group, or a resource in a different region than the Scenario targets.
Action timeline
The action timeline is a visual representation of when each Action started and ended relative to the overall run. Actions that run in parallel appear on the same time axis; sequential Actions appear in order.
The timeline helps you understand the temporal relationship between Actions. In a Compute Zone Down Scenario, for example, you can compare the virtual machine and virtual machine scale set shutdown Actions and see how long the combined disruption lasted.
Execution flow
The execution flow section shows the run's step and branch structure as a diagram. Each node represents a step or branch, annotated with its status and duration. This view is most useful for complex Scenarios that compose many Actions across parallel branches.
View reports
You can access Scenario reports in two ways:
- From the Workspace: Select Reports in the Workspace left navigation to see all completed runs across all Scenarios in that Workspace.
- From a Scenario: Open a Scenario and select a completed run to view its report directly.
Download and share reports
Select Download on the report page to save a copy. Downloaded reports can be shared with team members, attached to incident tickets, or archived for compliance records.
Note
Scenario reports contain resource names and identifiers from your Azure environment. Review reports before sharing them outside your organization.