Monitoring Azure Blob Storage Jobs

When you execute an object in Automic Automation, the corresponding task is visible in the list of Tasks in the Process Monitoring perspective. Process Monitoring gives you the full range of possibilities to monitor, analyze, identify, and remediate problems. It displays comprehensive data on active and inactive tasks, it provides tools to filter and group tasks. In this perspective, you can modify active tasks, open their reports, and execution lists and troubleshoot.

If you want to learn more about how to monitor your jobs, please refer to the Automic Automation product documentation at Monitoring Tasks.

For more information on how to work with tasks on the Process Monitoring perspective, refer to the Automic Automation documentation at Working with Tasks.

This page includes the following:

Monitoring Job Details

  1. Go to the list of tasks in the Process Monitoring perspective.

  2. Find the Azure Blob Storage task.

  3. Select the task and select the Details button.

    The Details pane opens on the right hand side and shows a summary of the execution of the selected task. The General and Job sections of the Details pane display information about the object configuration and its execution in Automic Automation.

    The Object Variables section displays the information that the Azure Blob Storage system reports back to Automic Automation for the following jobs:

    • Copy Job

      • &COPIED_COUNT#

        Shows the number of actually copied files.

      • &COPY_COUNT#

        Shows the number of files that match.

    • Delete Job

      • &DELETED_COUNT#

        Shows the number of actually deleted files.

      • &DELETE_COUNT#

        Shows the number of files that match.

    • Download Job

      • DOWNLOADED_COUNT#

        Shows the number of actually downloaded files.

      • DOWNLOAD_COUNT#

        Shows the number of files that match.

    • Exist File Job

      • &BLOB_EXIST

        The variable value is either true or false, depending on if the blob exists in the container or not.

      • &BLOB_COUNT

        The variable value is the number of blobs retrieved by the job.

    • Monitor Job

      • &FILE_URI#

        The variable value is the URI pointing to the respective blob in the container. This variable only has a value if you have selected the Return File URI option on the Monitor File Job definition. Otherwise, it remains empty.

    • Upload Job

      • &UPLOADED_COUNT#

        The variable lists the number of actually uploaded files.

      • &UPLOAD_COUNT#

        Shows the number of files that match.

Canceling and Restarting Jobs

You can execute Jobs and cancel/restart the corresponding tasks in the Process Monitoring perspective.

Canceling means that both the Automic Automation task and the job on the Azure Blob Storage environment are canceled. If canceling the execution fails (for example, if you do not have the rights to cancel the execution), the execution remains active and that information is visible on the job report.

For more information on how to work with tasks on the Process Monitoring perspective, refer to the Automic Automation documentation at Working with Tasks.

Agent Connection

If the Agent stops working or loses connection, the Job execution stops but resumes as soon as the Agent is connected again.

Reports

When jobs are executed, Automic Automation generates output files and reports that you can open from the user interface. Combined with the Execution Data, these reports provide comprehensive information about the status and the history of your executions. This information tracks all processes and allows you to control and monitor tasks, ensuring full auditing capability.

Reports are kept in the system until they are explicitly removed by a reorganization run. During a reorganization run, the Execution Data can be kept. Keeping the execution data is an advantage, because reports can consume a large amount of hard drive space. Removing the reports from your database does not mean loss of important historical data.

The following reports provide a comprehensive insight into the executions of your jobs:

  • Report (REP)

    This report provides information about the execution of the commands in the Job JCL. It contains all relevant information about the job execution and its results, no matter if it succeeds or fails.

  • Agent log (PLOG)

    This report logs all the functions that the Agent has executed for the specific Job. It contains the summary of the job configuration.

  • Directory

    This report provides the list of job output files that the job has created for this particular execution and that are available for downloading.

To Access the Reports

Do one of the following:

  • From the Process Assembly perspective

    • After executing a Job, a notification with a link to the report is displayed. Click it to open the Last Report page.

    • Right-click a job and select Monitoring > Last Report.

    In either case, the most recent report that is created for the object opens up.

  • From the Process Monitoring perspective

    • Right-click a task and select Open Report.

      The report of that particular execution opens up. Its runID is displayed in the title bar to help you identify it.

    • In the list of Executions for a particular task, right-click and select Open Report.

See also: