ServiceNow: Job finalized alert rule
This alert rule, specifically for ServiceNow integrations, enables users to easily setup a rule for failing backup jobs on primary servers, policies and/or schedules and create a ServiceNow incident.
Once the backup job is successfully executed, the ServiceNow incident is automatically tracked and marked as Resolved. However, a successful backup job means the first time the job ran successfully after one or more failures, for the same client-server pair that triggered the alert.
The alert rule, ServiceNow: Job Finalized, alerts on jobs of the selected product vendor and primary server that have completed with a specified Exit Status. For Veritas NetBackup, the scope can also include policy and/ or schedule. This alert also enables incident creation within ServiceNow for the selected scope.
Note:
For the ServiceNow: Job Finalized alert rule, Exit Status is a mandatory selection.
With this specific alert rule, there are some special considerations.
Policies and Schedules can be selected as part of the scope for data collectors, such as Veritas NetBackup and Backup Exec, where they exist. You can choose any product and their Primary Servers.
When defining the scope, you can choose a Server Type. This means that if Client is selected, then only those jobs will be alerted on where the Primary Server is not backing up itself. If any other Server is selected, then only those jobs will be monitored where the server is also the client (backing up itself). If this is skipped, then all the jobs will be reported as per the other scope filters.