For any Niagara provisioning job, you can configure it to generate an alarm either upon job failure, successful job completion, or both. For details, see alarm checkboxes (Niagara Network Job Builder) and alarm checkboxes (Niagara Network Prototype View).
Alarm routing uses the alarm class specified in the Supervisor’s BatchJobService properties, and any alarm appears as an Alert 
(source state) in the Alarm Console, showing the BatchJobService ord as source (local:│station:│slot:/Services/BatchJobService). See Figure 55.
The single alarm source of the BatchJobService applies to all Niagara provisioning related alarms (alerts), meaning only one row is used in the Alarm Console for all provisioning alerts. Keep in mind if there are multiple alerts, and you click on that row, all alerts will be acknowledged.As needed, double-click that row to see multiple provisioning alerts in the Alarm Details view for the BatchJobService, as shown done in Figure 55.
Note that as shown, each Niagara provisioning alert includes a hyperlink 
for more details. When you click the button with the alert highlighted, the view changes to either:
-
Batch Job Log File View — For that job, in cases where the alert is raised for successful job completion. For more details on this view, see Batch Job Log File View.
-
Batch Job Step Log File View — For a failed job step, in cases where the alert is raised for a job failure. For more details on this view, see Batch Job Step Log File View.
Figure 56 shows an example hyperlink to the step log file view for a failed Niagara provisioning job.
If you disposed a Niagara provisioning job before acknowledging it from the Alarm Console, if you click the button to it from an associated Alarm Details view, you will see a “Cannot Display Page” error in the view. This happens
because disposing a job removes the batch job log (.bjl) file and all batch job step log (.bjsl) files associated with that job. Therefore, it is recommended that you acknowledge any related alarms (alerts) before disposing
jobs.