Procedures in UpGuard provide an automated method of validating the execution of IT processes. This article covers the creation and basic concepts of UpGuard procedures.

Creating a Procedure

Getting Started

To create a new procedure, start by clicking the “Add Procedure” button in the top right of the dashboard.

w600

Procedure Constraints

A procedure is a set of steps. Procedures have a limit of five steps. This constraint encourages granular separation of concerns so that procedures stay targeted and avoid scope creep.

w600

Editing the Procedure Name

The procedure name is in the top left. Clicking on the name will make it editable. Moving focus away from the field will save the name.

w600

Adding to a Node Group

Procedures are used to assess nodes and as such are inherited through node groups. Below the procedure name is the field to assign it to a node group. procedures cannot be added to multiple node groups at once but after creating a procedure a copy is saved to the Library, from which it can be added to other node groups.

w600

Step Types

Currently, procedures support the step type of Policy Run. Additional steps coming soon include making an API call, pausing for manual validation, and running a node scan.

w600

Policy Run Steps

Users can select from all custom policies in their organization for Policy Run steps. The step will use the node’s most results for that policy to evaluate whether it has failures.

w600

Actions on Failure

The last step of a procedure is to send a message on failure. These can be sent via email or by using one of UpGuard’s supported integrations.

w600

Editing a Procedure

Editing a procedure returns you to the same screen as when creating a procedure. You can remove steps, add steps, and change the name of steps by clicking on their name.

w600

Tags: