The Auto-Triage function serves to identify the root causes and obtain more information about an issue.
Once Auto-Triage identifies an issue, it will run the investigative steps that are normally run manually. These steps generally include gathering additional contextual diagnostics information, conducting analyses and performing common troubleshooting tasks.
ATEs (Auto Triage Elements) may be set to run automatically or manually. In v7.1 Auto-Triage is enabled and sets ATEs to run manually by default.
When an ATE is available to be run or when results are ready to be viewed, the Auto-Triage icon will appear alongside the issue headline in the Issues Page.
In 7.3, click on the “Issues with Auto-Triage” box to retrieve the list of issues with ATE.
To configure Auto-Triage, navigate to the Application Settings tab
Select the desired setting:
Automated – run ATEs automatically
Manual – run ATEs on demand
When ATEs are set to run manually, they may be triggered by users.
To manually trigger an ATE, navigate to the issues page, identify an issue for which a playbook is available and run the playbook by selecting the Auto-Triage button.
Viewing ATE results is possible by selecting the issue. The pane on the right shows a quick summary of the information available following the running of the ATE.
For a more elaborate version of the information gathered by the ATE, navigate to the Auto-Triage tab by clicking on the LEARN-MORE button on Auto-Triage section
The Auto Triage tab is divided into 2 sections:
The left-hand side displays Issue Diagnosis and Remediation Steps. If there are issue items, click on the Down Arrow to select the issue item of interest. Issue Diagnosis shows the results of the investigation and provides the conclusion that was reached for the issue or issue item. Remediation Steps provide steps to actively remediate the issue or issue item.
Issue Investigation on the right-hand side displays the investigative steps and it is designed for you to explore the steps taken by the Indeni system. Each interaction with the device is laid out in sequential order, allowing you to review each step taken by the ATE. The actual investigation is highlighted so you easily follow the actual steps. Click on a box on the workflow diagram to see each command we issued along with the output of the commands. You can also see the result of the decision of each step.
Prior to 7.3, when an issue with multiple issue items is detected, the system executes the ATE for each issue item. You can view the ATE results for all issue items. If another issue item is subsequently added, the system does not re-run the ATE for that new item.
In 7.3, we introduced the re-run capability. When the new item is added to the parent issue, the system will re-run the ATE automatically. This re-run will perform triage for every issue item, not just the newly added issue item provided the issue item(s) are still active and they have not been resolved. The system will save the results of every run for every issue item, up to 20 copies of re-runs. Viewing previous ATE results is possible by selecting the previous Run #.
In 7.3, you can also manually trigger a re-run by clicking on the blue “RE-RUN AUTO-TRIAGE’ link. If “RE-RUN AUTO-TRIAGE” is greyed out, that implies the issue has been resolved and you will not be able to re-run the ATE. The manual re-run will trigger the re-run at the parent issue level. The child issue item(s) will be re-run if they have not been resolved.