Example, when the Job is canceled or aborted. Generate: On error only means that the process log is kept when an error occurs. Generate: Always means that the process log of the operating system is always written. Store to: File means that the process log is stored as a file on the target system (Agent).If it cannot be deleted due to an error, the deletion process is not repeated and an error message is displayed. After the Automation Engine has written this data to the database, the report is automatically deleted from the Agent computer. When a Job has been executed on an Agent, the corresponding report is stored on the Agent computer. Store to: Database means that when the Job has been executed, the process log available on the target system (on the Agent) is stored in the database. You can select one or both simultaneously: When you configure a Job, you define where to store the Job report and when to generate it in the Job Report section on the platform-specific page. On this page you specify where to store the job, when to generate it and whether they include Agent log information. The Job report contains logs of every failed task.
Selecting this option may result in very large reports. The Job report contains the logs of every sub-task in the DAG task. The report contains only a summary of tasks and their status. Specify whether the task logs should be added to the Job report: Note: This list is populated only after you have entered the location and name of the Google Cloud Composer environment. Once you have found the one you need, click Choose. To search for a DAG, start typing its name to limit the list to the DAGs that match your input. Here you select the Run DAG job in the configured location and environment that this job will start and monitor.Ĭlick the button to open a dialog with the list of all available Airflow DAGs on the Google Cloud Composer environment. Name of the Google Cloud Composer environment. Region for the Google Cloud Composer environment. On the Run DAG page you enter the parameters that identify the Airflow DAG that the GC Composer Job will control.
In addition, an Automic Automation Run DAG Job consists of the following specific pages that we explain in this topic: Standard pages that are always available, no matter what type of object you are defining:Īdditional pages that are always available for executable objects: This page includes the following: Defining Automic Automation GC Composer JobsĪn Automic Automation Run DAG Job definition is made up of the following pages:
0 kommentar(er)
