Remedial actions using Playbook
Summarize
Summary of Remedial actions using Playbook
Remedial actions using Playbook in ServiceNow’s Investigation Framework enable you to resolve Configuration Item (CI)-related issues directly within the Investigate tab of the Incident record page. These actions, such as ending a process or restarting a service, provide interactive, guided remediation steps through a playbook interface accessible from the contextual side panel. This capability helps streamline incident resolution by controlling and tracking each step of the remediation process.
Show less
Key Features
- Playbook Integration: Playbooks guide the execution of remedial actions step-by-step, allowing you to monitor current and historical remediation processes on affected or caller CIs.
- Remedial Actions Available:
- End process: Stop processes on CIs, with specific workflows for Device and Server classes (including user approval or change request creation).
- Restart service: Restart services on CIs, also requiring user approval or change requests depending on the CI class.
- Contextual Side Panel: Access and execute playbooks, view current and historical remediation actions, and manage ongoing remediation through controls such as canceling actions.
- CI Scope: Remedial actions can be performed on both affected CIs and caller CIs associated with the incident, supporting device endpoints (DEX) and Service Operations Workspace (SOW) views.
- Concurrency Controls: By default, concurrent or duplicate remedial actions on the same CI are prevented, but you can configure the system to allow concurrent executions if needed.
Practical Use and Configuration
- The Investigation Framework and Remedial Action Framework applications must be installed and configured to enable this feature.
- Remedial actions appear on the Investigate tab only if configured to display, and the playbook interface is available on the Incident record’s side panel.
- For servers, executing remedial actions requires creating and providing information for a standard change request, ensuring compliance and governance.
- User approval is required before executing remedial actions on device endpoints, adding an additional control layer.
- You can view and manage remedial action statuses such as New, In Progress, Completed, Canceled, or Failed within the playbook panel tabs.
Key Outcomes
- Accelerate CI issue resolution by performing guided remedial actions directly from the incident interface.
- Maintain control and visibility over remediation steps and their statuses through the playbook’s current and history views.
- Ensure compliance with change management processes by integrating change requests for server-related remedial actions.
- Improve incident handling efficiency by allowing remediation on both impacted and related caller CIs.
- Customize remediation concurrency settings to fit your operational needs and reduce potential conflicts.
Resolve the CI-related issues using the remedial actions using Playbook in the Investigate tab.
- End process
- Restart service
- The Investigation Framework [sn_invest_fwk] application is installed and configured. For more information, see Setting up Investigation Framework in Service Operations Workspace and Configure the Remedial Actions Framework.
- The remedial actions are configured to display on the UI. For more information, see Customize the Investigate tab.
- Current: Displays the current list of playbooks that trigger the remedial action, including both processes and services run on the affected CIs or caller CIs with status New and In Progress.
- History: Displays the historical list of playbooks, remedial actions including both processes and services run on the affected CIs or caller CIs with status Completed, Canceled, or Failed.
- The remedial action is already in Canceled status.
- The corresponding CI action record of the remedial action is already in progress.
- The change request has already moved to implement state for actions associated to CIs of type server.
The Remedial actions section on the Investigate tab also contains the Current and History tab to display the list of remedial actions performed. By default, this section displays the list of remedial actions for the primary CI or current CI. You can switch the Show actions performed on all CIs in this incident toggle to display the list of remedial actions for all the CIs associated with the Incident.
Playbook is available only if both the Remedial Action Framework [com.snc.sn_reacf] application and the Investigation Framework [sn_invest_fwk] application are installed and configured, as well as if the remedial actions are triggered.
End process
- Top processes By Memory
- Top processes By CPU
- Device: For this CI class, a two-step process is executed where you must get the user approval before the End process remediation process can be executed. After it’s approved, you can directly stop the process on the device, which is also known as the endpoint.
- Server: For this CI class, you must create a change request before the End process remedial action can be executed using a standard change request. You must also provide additional information to create a change request.
Restart service
The Restart service remedial action is available with the Services metric information card.
- Device: For this CI class, a two-step process is executed where you must get the user approval before the Restart service remediation process is executed. After it's approved, you can directly restart the services on the device, which is also known as the endpoint.
- Server: For this CI class, you must create a change request before you can execute the remedial action using a standard change request. You must also provide additional information to create a change request.