Monitor
These topics are a Getting Started guide for both developers and object designers, and for operators (business users) and managers. From an object designer perspective, monitoring objects after creating and configuring them is key to ensure that they behave as expected. From an operator and manager perspective, your daily business consists of monitoring and analyzing tasks (both active and ended) and reacting in case of problems, in accordance with your rights and privileges.
If you have not read the Design section of the Getting Started guide yet, do it now. In this section, we will refer to the objects that we have created there.
Automic Automation has various monitoring options. We will concentrate on the Process Monitoring perspective, as this is where you have all available monitoring tools and functions. The My Catalog Perspective perspective is also a valuable dashboard for monitoring the tasks you are entitled to work with. However, as it provides less functionality, we will not deal with it in this Getting Started. For more information about it, see My Catalog Perspective.
Monitoring Tools in the Process Monitoring Perspective
The Process Monitoring perspective provides multiple monitoring tools:
As soon as an object is executed, it is displayed as a task in the Process Monitoring Perspective, where you can check its status and the status of its children (if available). The Task List provides key execution and status data. From this list you access all functions available for the task. For more information see Task Status and its sub topics.
The Reports give you detailed information about each execution of a task. You access them from the following places:
- Process Assembly
- Process Monitoring
- Global Search dropdown list
- Advanced Search result list
- All combo boxes that let you select executable objects. For more information, see Using AWI Combo Boxes.
We have already checked the reports after executing the JOBS.WIN.RETRIEVE.FREE.DISKSPACE Job that we have created and enhanced in the Design section of this Getting Started guide, see:
- Check the Report (basic)
- Execute the Job and Check the Report (enhanced)
- Execute the Job and Check the Report Again (enhanced after adding the variable)
For more information about reports in general in this documentation, see:
The lists of Execution Data provide the details of all past executions of a particular task (and/or of its children, parent or activator). You access them from the same places as the reports. As with the reports, after executing the JOBS.WIN.RETRIEVE.FREE.DISKSPACE Job in this guide we already checked its execution data, see Open the List of Executions.
Use the lists of executions when you troubleshoot to compare the different runs (for example, the failed run and a successful one) of a task. Use these lists in combination with the reports and the information provided by the task details to get a clear picture of what has happened.
For more information about execution data in general in this documentation, see Execution Data. For more information about object and task details, see Viewing Object and Task Details.
Not all tasks have a dedicated monitor view. For some task types, all the information you need is already contained in the list of Tasks, on the reports and in the Executions lists.
The following task types require more extensive information for monitoring and they provide a dedicated monitor:
- Workflows
- Schedules
- Jobs if they have a JCL
- SLM Services provided by SLO objects
If you have the necessary rights, you can also perform various operations with the tasks. Take a look at Working with Tasksfor a description of the available functions.
Monitoring
When we created the objects in the Design section of this guide, we already had a look at some of Automic Automation's monitoring tools, namely the list of executions and the reports. Click the links below to know more about Automic Automation's monitoring capabilities: