Remediation

When the presence of an alarm is confirmed, the pilot handling the alarm must have an action plan.

The tasks in this remediation workflow can be carried out either manually or automatically, if the environment allows.

Our module of remediation guidelines therefore features an instruction editor for:

• Define each action required and the expected result
• Associate a scheduler task (to automate execution)
• Define average guideline application time

The pilot can:

• Check off the fact that he has performed an action
• Suggest a more appropriate execution time
• Evaluate and propose guideline improvements

Finally, the module records the time taken to resolve the alarm since the action plan was executed. This information will be used by the Pilot experience module to capitalize on this experience in general.

Updates 2022: In addition to Rundeck and AWX schedulers, Canopsis can also perform Jenkins and Visual TOM jobs in remediation.

Update 2025 : Retry policy for failed remediation guidelines

When configuring a remediation, it is now possible to define a timeout period. Once this time has elapsed, Canopsis checks the alarm status to determine whether the remediation has been effective.

If this is not the case, define a retry policy to restart remediation automatically.

A new remediation attempt can also be retried when a specific event occurs on the alarm, such as:

• change in criticality (increase, decrease or modification via dedicated action)
• standby exit
• start or end of a periodic behavior
• reception of a new “check” event…

Update 2025: Possibility of receiving remediation notifications.

For more information on remediation, visit the Canopsis documentation.