Monitoring AWS Lambda Jobs

When you execute AWS Lambda jobs to trigger a Lambda function, the message pane and the Job reports will only inform you whether the job has been executed successfully. All the Job details will be available in your AWS Lambda system. Automic Automation does not monitor your AWS Lambda Jobs

This page includes the following:

Restarting AWS Lambda Jobs

AWS Lambda Invoke Jobs cannot be restarted. Clicking the Restart button triggers a new Job run.

AWS Lambda 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:

Agent log (PLOG)

This report captures everything that has to do with the Job execution from the Automic Automation perspective: When the Job started, the Job configuration parameters, whether there has been any validation and its results, and so on, It also contains the response received from the target system but in a format that cannot be parsed for further processing.

Since this report logs all that happens during the execution, it is your first place to go if you need to troubleshoot issues, also if those issues have to do with the configuration of the Job. For example, if you use variables to populate the configuration fields, these variables are resolved at runtime. This report show the actual variable values and not their names.
Report (REP)

This report is empty unless the Invoke Lambda job uses the RequestReponse Invocation Type with the Tail Logs option checked. If so, this REP includes additional execution information.
Agent log (LOGS)

This report provides the Lambda-specific logs for the particular job, such as the execution log if the Tail Logs checkbox is activated.
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 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.