After the RCA is complete, the workflow may continue with another operational task.
Depending on the incident, Aiden can:
These tasks usually follow the same process for similar incidents, making them good candidates for automation.
Some remediation workflows require human approval before they run.
Here, Aiden asks whether it should create a ServiceNow incident and include the RCA. After you approve the request and specify the assignment group, Aiden continues with the workflow.
The approval step is part of the Skill. You decide which actions run automatically and which wait for approval. Once that policy is in place, Aiden follows it every time the Skill runs.
If you've already defined how a particular incident should be handled, there's no reason to recreate that workflow every time it occurs.
Skills give Aiden a predefined workflow to follow. Instead of deciding the next step during the investigation, Aiden executes the process you've already defined for that type of incident.
A Skill defines:
The RCA and findings may change from one incident to the next, but the workflow stays the same.
ServiceNow is the example in this walkthrough, but the workflow can extend to any integration connected to Aiden.
A Skill can define actions such as:
You choose which actions belong in the workflow and where approval is required. Aiden follows that Skill every time.
A root cause analysis explains what happened. The next operational step determines how your team responds.
With predefined Skills, Aiden can continue from RCA to ticket creation, remediation, or another operational workflow while following the approval process your team has already defined.
Schedule a demo to see how Aiden handles incident remediation in your own environment.
Aiden doesn't decide the next step on its own. Each follow-up action comes from a predefined Skill that specifies what to do after a particular type of incident, whether that's creating a ServiceNow incident, triggering a runbook, or another operational task.
The answer depends on the action. Many teams are comfortable with automatic ticket creation, while production changes often require an engineer's approval. Approval rules are defined as part of the Skill, so the same policy applies every time it runs.
The walkthrough uses ServiceNow as an example, but the same approach works with any integration connected to Aiden. A Skill can trigger Kubernetes runbooks, execute operational commands, or start other workflows that are part of your incident response process.
Not necessarily. A Skill represents the workflow for a specific category of incidents. Similar incidents can follow the same Skill, while different incident types can have their own workflows and approval policies.