Configuring BMC TrueSight Infrastructure Management Server for the triage and remediation
In the BMC TrueSight Infrastructure Management Server, the parameters of the manual, on-demand OS Disk Space Full workflow are contained in the following extract from the installationDirectory\pw\server\etc\cellName\kb\bin\ao_actions.mrl file.
{
['Administrator', 'Full Access', 'Data Collection Administrator', 'Event Administrator', 'Event Operator', 'Data Collection Operator', 'Event Operator Supervisor', 'Data Collection Supervisor']
}
[
'Create Change Request':MC_TRUEFALSE($CREATECHANGERQUEST),
'Change Request Type':MC_CHANGEREQUESTTYPE($CHANGEREQUESTTYPE),
'Create/Update Incident' : MC_TRUEFALSE($CREATEINCIDENT),
'Remediate' : MC_TRUEFALSE($REMEDIATE)
]
:EVENT($EV) where [ $EV.status != 'CLOSED' AND $EV.status != 'BLACKOUT']
#If you want this action to be context sensitive to PATROL Events monitoring Disk usage.
#Comment above line and uncomment below line.
#:PATROL_EV($EV) where [ $EV.mc_parameter within ['LDldDiskSpaceUsed' , 'LDLogicalDiskspace' , 'FSCapacity' , 'LDldFreeSpacePercent'] ]
{
action_requestor($UID,$PWD);
opadd($EV, "Triage and Remediate Disk Full manual", $UID);
admin_execute(BEMGW,$EV,"Atrium_Orchestrator_Disk_Full_Workflow",[$CREATECHANGERQUEST, $CHANGEREQUESTTYPE, $CREATEINCIDENT, $REMEDIATE,$UID],YES);
}
END
You can make the launch of this on-demand workflow a right-click, context-sensitive option for PATROL events by commenting and uncommenting the specified lines of code, as shown in the following extract:
#If you want this action to be context sensitive to PATROL Events monitoring Disk usage.
#Comment above line and uncomment below line.
:PATROL_EV($EV) where [ $EV.mc_parameter within ['LDldDiskSpaceUsed' , 'LDLogicalDiskspace' , 'FSCapacity' , 'LDldFreeSpacePercent'] ]
:PATROL_EV($EV) where [ $EV.mc_parameter within ['LDldDiskSpaceUsed' , 'LDLogicalDiskspace' , 'FSCapacity' , 'LDldFreeSpacePercent'] ]
You can customize this example to make a workflow context-sensitive to the disk-full event used in your environment.
When you manually launch this workflow from the Events Console of the operator console, you must enter the following input parameters in the Execute Action dialog box, as shown in the following table:
Workflow input parameters
Input parameter | Description |
|---|---|
Create Change Request | Boolean. True/false indicator that shows whether you want to create a change request in BMC Remedy Change Management System. If you choose false, the Change Request Type parameter is ignored. |
Change Request Type | String. Specifies the type of change request (normal/preapproved) |
Create/Update Incident | Boolean. True/false indicator that shows whether you want to create an incident in the incident management system. If an incident already exists, then workflow updates the existing incident information. |
Remediate | Boolean. True/false indicator that shows whether you want to proceed with the remediation action. |
The values that you enter in the Execute Action dialog box are captured in the event definition by the mc-action-args slot, which contains five argument variables. The following example shows the input arguments of an mc-action-args slot from a PATROL event.
</mc-action-args>
The arguments apply to the input parameters in the order that the parameters are listed in the Execute Action dialog box. In this example, Create Change Request = true, Change Request Type = normal, Create/Update Incident = true, and Remediate = true
The parameters of the automated remote action policy workflow are contained in the following extract from the ao_actions.mrl file:
{
['Administrator', 'Full Access', 'Data Collection Administrator', 'Event Administrator']
}
:EVENT($EV) where [ $EV.status != 'CLOSED' AND $EV.status != 'BLACKOUT']
{
opadd($EV, "Triage and Remediate Disk Full Auto", "BMC Impact Manager");
admin_execute(BEMGW,$EV,"Atrium_Orchestrator_Disk_Full_Workflow",[
"true","normal","true","true","BMC Impact Manager"],YES);
}
END
The ao_actions.mrl file contains the following default values for the automated workflow launch in the admin_execute argument:
Input parameter | Default value |
|---|---|
Create Change Request | True |
Change Request Type | Normal |
Create/Update Incident | True |
Remediate | True |
After extracting the configuration data from the event, the common framework determines the logging level for the workflow, sets the level at normal or detailed, and updates the event information in the Notes dialog box of the operator console accordingly.
You can override the default values by manually editing the ao_actions.mrl file for automated workflows. After editing the ao_actions.mrl file, you will need to recompile the knowledge base (KB) of the BMC TrueSight Infrastructure Management Server cell and then restart the server cell. (For the steps, see Configuring the BMC TrueSight Infrastructure Management Server cell.)