Monitoring K8s Jobs

monitoring Kubernetes jobs, monitor Kubernetes 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.

This page includes the following:

Monitoring K8s Job Details

monitoring Kubernetes job details, monitor Kubernetes job details

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

  2. Find the K8s task.

  3. Select the task and select the Details button to open a pane with information about the task execution.

    The General and Job sections of the Details pane display information about the object configuration and its execution.

    The Object Variables section displays the response from K8s for the Run Jobs. The response does not include any Pod logs.

Canceling K8s Jobs

cancelling Kubernetes jobs, cancel Kubernetes jobs

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

Canceling means that the Automic Automation task is canceled as well as the job on the K8s environment. If for some reason 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.

K8s Agent Connection

Kubernetes agent connection

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

K8s Reports

Kubernetes 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, combined with execution data, offer comprehensive information about the status and history of executions, ensuring full auditing capability:

  • Agent log (PLOG)

    This report captures everything that has to do with the Job execution from the Automic Automation perspective:

    It provides a comprehensive log of a Job’s execution, detailing its start time, configuration parameters, validation results, and the response from the target system, though the response is in an unprocessable format.

    It serves as the primary resource for troubleshooting issues, including those related to Job configuration. For example, it shows the actual values of variables used in configuration, rather than their names, as these are resolved during runtime. Additionally, the agent log includes all parameters used during execution, execution results, the final integration URL, and the various job states throughout the process, which aids in identifying and addressing potential problems.

  • Report (REP)

    This report captures information that the target system sends to Automic Automation during and after Job execution. It provides relevant information about the Job execution and its results in a format that can be easily parsed for further processing, such as JSON or XML. This report's content can be used to trigger further actions based on that content.

    Note:

    The Report (REP) cannot be parsed if the job throws an exception. In this case, only the exception message is written into both the Report (REP) and Agent (PLOG) logs.

    You will most probably include the Jobs in other Automic Automation objects such as Workflows or Schedules to orchestrate operations. When you do so, you can use the content of this report on the Post Process pages of the Job definition to trigger further actions based on that content. For more information see, Process Pages in the Automic Automation product documentation.

  • Directory

    This report provides a list of job output files created during a particular execution and available for downloading. It may also contain files downloaded from the target system.

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 for that particular execution opens. 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: