Action configuration in IF:-
This document is to help users to configure automated actions in InsightFinder. These automated actions get triggered based on predicted incidents.
Option 1 – Configure the action in project settings – User can set up all possible actions in this section which will be available system wide to configure for different scenarios.
- Go to “Settings” -> “System Settings”.
- Select the required “System” and then the required “Project”.
- Once you are in the project, you need to select the “Actions” tab.
- On that page, you can click on “Add” to configure a new action. You need to provide
- Action name – You can choose your action name
- Command – You need to provide the command that you want to run to execute your action
- Script file name – You need to provide the file name (just name) of the script. The path of the script will be picked from script runner. Refer here – https://insightfinder.com/resource/automations/script-runner/
- Script parameter – Provide any parameters that you need to pass to run the action script.
- Click on “Update” at the bottom of the page and your action would be configured.
Please Note – This action is for the specific project and the instance selected in the dropdown at the top of the page.
Option 2 – Configure actions in Knowledge Base – User can set up actions in the knowledge base section. These actions will be specific to a particular root cause and predicted incident and will be auto trigger or can be manually triggered.
- Go to “Knowledge Base” from the left menu.
- Select the “System” in the top drop down and the “Project” from the drop down menu below it.
- All the knowledge base entries will be listed.
- You can click “Configure Action” against the root cause and incident that you want to configure.
- This pop will have options to select the action previously set up or configure a completely new action using the “Add Action” button. Adding a new action is the same as in Option 1 where in pop up you need to select the project and provide action name, command, file name and parameters.
- Now you will have this action also appear in the dropdown on the previous pop -up and you can select the required action. Also select the server where the script runner is running.
- Once saved, this will be used to trigger action for this root cause and incident automatically. You can see this saved action in the “Saved actions” section.
Option 3 – Configure action in Incident Investigation page – User can configure required action directly in the incident investigation page. This is the most granular level to configure an action for a scenario. Users can also trigger an action immediately from this page.
- Go to the “Incident Investigation” page from the left menu.
- Select the incident, then “Actions” toward the right and click on “Configure Action”
- Here user can either select the existing action by clicking in the “Action” box or create a new action by clicking on the “+” next to Action.
- Once you have created or selected an action, you can do a one time trigger or configure for auto-trigger in future for this incident. You can do this by selecting the field next to the Action field.
- You also need to select the Instance Id. This can be a “dynamic instance targeting” which means the action will be executed on the impacted instance only or “Apply on all instances” which means the action will be executed on all the instances in this project.
- Next, you can configure to notify people by providing their email id as a comma separated list in the “Notification recipients” field.
Select the server where the script runner is running in the “Action server” dropdown.
“Save action” or “Take action” would be enabled or disabled based on where it’s one time action or always. If the user saves the action, it will appear in the “Saved actions” section on the top of this pop -up.