Preventive Profiles
Preventive Check is a feature that lets you select some of the commands registered in a Network Automation task as check items, map judgment rules to each item, and automatically evaluate the execution results. Every time the task runs, a report is generated that automatically judges each item as normal, warning, or critical according to the mapped rules — so you can standardize repetitive checks and detect threshold-based anomalies without manual review. It's intended for network administrators and infrastructure engineers who repeatedly inspect network devices.
Profiles are check templates for Preventive Check. A profile defines which automation task's commands to use as check targets, and which item label and judgment rule to apply to each command's result.
Viewing the profile list
Go to Network Automation > Preventive Profiles to view the list of registered profiles. You must first select an NMS Manager from the Select Manager dropdown at the top of the screen for the list to appear.
Key list information
| Column | Description |
|---|---|
| No. | List sequence number |
| Profile | Profile name. Click to open the edit popup |
| Automation task | Device alias or host of the automation task linked to the profile |
| Target | Device address the task actually connects to |
| Commands | Number of check commands registered in the profile |
| Latest report | Status badge (Normal·Warning·Critical·Unknown) and creation time of the most recently generated report |
| Profile enabled | Shows enabled status as an Enabled·Disabled badge. Cannot be toggled directly in the list — change it only in the edit popup |
| Actions | View details, edit, and delete icons. Both view details and edit open the same edit popup |
Type a profile name in the search box to narrow the list instantly.
Adding or editing a profile
-
Click the Add Profile button at the top right. To modify an existing profile, click the Edit icon in the list instead.
-
Configure each field in the popup, then click Save Profile.
Step 1: Enter basic information
| Field | Required | Description |
|---|---|---|
| Profile name | Required | Name to identify the check template |
| Automation task | Required | Select the automation task to use as the check target. Tasks already used by another profile are excluded from the list |
| Profile enabled | Enable toggle, enabled by default | |
| Memo | Write a description memo for the profile |
Once you select an automation task, a summary card shows the selected task's CLI driver, schedule, latest execution result, and command count.
Step 2: Mapping check items
The commands registered in the selected automation task appear in a table in execution order. Configure the check method for each command in its row.
| Column | Field | Description |
|---|---|---|
| Use | Checkbox | Unchecked commands are not saved to the profile |
| Automation command | Text (read-only) | The original command registered in the task |
| Item label | Input field | Enter the check item name to display in the report |
| Use parser | Dropdown | You must select Use to select a Match field below |
| Match field | Dropdown | Select the column, parsed from the command execution result, to use for judgment. If parsing failed for a command, enter the value manually |
| Applied rule | Dropdown | Select the judgment rule to apply to this item. If there is no rule, select No rule |
Click the Manage Rules button at the top right to open the rule edit popup layered over the profile edit popup. You can register a new rule and immediately select it in the Applied rule dropdown.
If the command execution result is parsed into a table, the Match field dropdown is automatically filled with the actual column names. If parsing failed, enter the value directly into Match field.
Deleting a profile
-
Click the Delete icon in the list to open a confirmation dialog.
-
Click confirm to delete the profile.