Assessments
Assess your application deployment's resilience posture by evaluating performance against predefined requirements.
A resilience assessment is a structured evaluation of how well an application deployment aligns with defined resilience goals such as availability, maintainability, and integrity. These goals are configured through resilience posture plans which pair a selected resilience profile (a set of requirements and metrics) with a target application deployment. Assessments compute requirement-level scores, estimate potential disruption cost, and generate recommendations to address gaps and improve your overall application deployment resilience posture.
Note: When upgrading your Concert instance from v1.x to v2.x, existing resilience data is not retained. After upgrading, recreate your resilience configurations in the new version.
After creating a resilience posture assessment plan, which defines the parameters for assessing the resilience of a specific application deployment, you can provide resilience data and run assessments using any of the following methods:
- Using Concert Workflows: You can import prebuilt workflows from a library, configure them in your Concert Workflows instance to ingest resilience data from an external source, and schedule a workflow job to do so on a recurring basis. The latest ingested data is referenced by Concert when creating resilience assessments, which occurs at the defined aggregation period.
- Manual data entry: If you do not have a set aggregation period in the posture plan or there is no assessment in progress, you can enter data manually in the within the posture assessment details page by clicking Create assessment or using the
/evaluateAPI.Draft comment: erin.pelkey@ibm.com
It's unclear how the /evaluate API is supposed to be used. Is this for scheduling continuous resilience assessments or running one-time assessments? - Using the Discover your data feature: From the Concert home page, you can click Discover your data to quickly ingest application deployment and resilience data from a connected cluster — for example Amazon Elastic Kubernetes Service (EKS) or IBM® Cloud Kubernetes Service (IKS) — automatically discovers application deployments based on provided credentials and label configurations. The process provisions required resources, discovers running workloads, and surfaces a summarized view of resilience posture across all discovered application deployments.
Draft comment: erin.pelkey@ibm.com
This describes the ingestion process, but how does this turn into or relate to resilience posture posture assessments? What does the user need to do to configure this?
How do you actually run the assessment or when does Concert know when to do so? I'm confused if the assessment period defined in the posture assessment plan determines how frequently the assessment will run. During the demo, someone mentioned this assessment period just determines how data is aggregated in the assessment, not how often the assessment actually runs. Please advise. If this isn't how they schedule an assessment, how do they do that?