Resilience actions
Resilience actions help you identify and remediate issues that affect the resilience posture of your application deployments. Concert generates actions from assessment results to highlight risks, missing data, configuration issues, and recommended improvements.
Before you begin
- You must have the appropriate permissions for the application deployment and environment.
- Users with Admin or Editor access can view resilience actions and generate resilience action plans.
- Users with Viewer access can view resilience information but cannot generate or manage resilience actions.
- Resilience actions are available only for supported resilience assessments that contain the required assessment data.
Types of resilience actions
- GenAI resilience actions provide AI-generated recommendations and summaries based on assessment results, resilience requirements, libraries, and component data.
- Rule-based resilience actions provide recommendations when predefined resilience rules detect specific operational conditions, configuration issues, or deployment-level risks.
- Missing metrics resilience actions identify required metric data that is missing from an assessment and help improve assessment completeness.
Lifecycle of resilience actions
The Status column in the Action center indicates the current lifecycle state of a resilience action. Resilience actions are automatically reevaluated when resilience assessments are rerun. Based on the latest assessment results, Concertupdates the action status to reflect the current resilience posture of the application deployment.
- Created: Indicates that a resilience issue, missing metric, or rule condition is currently detected and requires attention.
- Example: A resilience assessment identifies that CPU limits are not configured for a deployment and generates a Configure CPU Limits action with a status of Created.
- Success: Indicates that the issue is no longer detected in the latest assessment results.
- Example: After CPU limits are configured and a new assessment is run, Concert no longer detects the issue and updates the action status to Success.
- Closed: Indicates that the action is no longer applicable or has been replaced by a more specific action.
- Example: An assessment initially generates an application-level action because component-level assessment data is unavailable. After a later assessment includes component-level data, Concert can generate more specific component-level actions and mark the earlier application-level action as Closed.
This automatic lifecycle helps ensure that resilience actions remain aligned with the latest assessment results and current application posture.
Resilience action plans
For supported resilience actions, you can generate a resilience action plan that provides detailed remediation guidance and implementation steps to help resolve identified resilience issues. Action plans are generated from resilience actions and provide additional implementation guidance beyond the recommendations shown in the action itself.
For more information, see Generating a resilience action plan.
Why resilience actions matter
Resilience actions help you understand why a resilience score was impacted and what steps can be taken to improve it. By identifying configuration gaps, operational risks, deployment-level issues, and missing assessment data, actions provide clear guidance that helps you prioritize remediation efforts and strengthen the resilience posture of your application deployments.
Hey @raghvendra and @akansha, please check this pre-reqs. I have drafted this but not very sure if it's 100% accurate or not. Please let me know. Thank you!