Remediation Workflow Template

You use the AIOPS Workflow template to create remediation Workflows. You select this template on the Add Object dialog when you start to define the Workflow.

The AIOPS template is pre-configured. It creates a Workflow that already contains the first task, which is itself a Workflow called PCK.AUTOMIC_AIOPS_SHARED.PUB.ACTION.PARSE_JSON_INTO_VARIABLES.

The purpose of this Workflow is to parse the data of the alarm provided by the JSON payload into variables. The remediation Workflow uses these variables for its execution. You add the tasks you need after this first Workflow.

This is what it looks like:

Screenshot showing the Workflow editor that is displayed right after selecting the AIOPS template for creating a Workflow. It shows the pre-configured first Workflow.

Where Can I See the Parsing Details?

You find the parsing details here:

  • Workflow editor (Process Assembly perspective)

    1. Go to the Process Assembly perspective and right-click PCK.AUTOMIC_AIOPS_SHARED.PUB.ACTION.PARSE_JSON_INTO_VARIABLES in the Workflow editor.
    2. Select Properties to display a pane with the tabs that contain the task properties.
    3. The Variables and PromptSets tabs display the variables and PromptSets used to parse the incident data.

  • Workflow monitor (Process Monitoring perspective)

    As soon as a remediation Workflow starts executing, it is visible in the Workflow monitor. You can also access the details of the payload from the Workflow monitor. You see the raw JSON payload in the Object Variables section in the Details pane of the pre-configured Workflow. The variable that contains it is called &UC4RB_AIOPS_JSON_LOAD#.

Example of a JSON Payload

This example illustrates a parsed JSON payload:

{

"alarmId": "8aaf105eaaae48b79ef1285ef0eb287c",

"productId": "ao",

"docTypeVersion": "1",

"robot": "SuperDomain",

"host": "node2",

"rootCause": false,

"metId": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact",

"ci_unique_id": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact",

"ci_id": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact",

"docTypeId": "itoa_alarms_anomaly",

"status": "NEW",

"origin": "node2",

"metricName": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact:Total GC Time (ms)",

"severity": "major",

"sourceProduct": "Application Performance Management",

"csId": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent",

"ciName": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent",

"message": "Total GC Time (ms): Probable Anomaly (outside 95th percentile probability range) detected",

"alarmType": "Anomaly",

"problem": false,

"deviceId": "APM$$host$$node2",

"deviceName": "node2",

"actionsSupported": {

"acknowledge": true,

"unAcknowledge": true,

"ticket": true,

"assignment": true,

"unAssignment": true,

"clear": true,

"visible": false,

"invisible": false

},

"automicJobs": [],

"troubleTicketUrl": "",

"product_id": "ao",

"doc_type_version": "1",

"met_id": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact",

"ciUniqueId": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact",

"doc_type_id": "itoa_alarms_anomaly",

"metric_name": "SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent|GC Monitor|Garbage Collectors|MarkSweepCompact:Total GC Time (ms)",

"timeOrigin": "1580213400000",

"tenantId": "F4BFCADF-374C-4675-9962-5261B6A5D2F4",

"ciId": "APM$$host$$node2$$agent$$SuperDomain|node2|KubernetesUMA112030|Kubernetes Agent$$GC Monitor$$Garbage Collectors$$MarkSweepCompact$$Total GC Time (ms)"

}

See also: