为什么在Cloud Composer中自动生成一个名为"airflow

本文介绍了为什么在Cloud Composer中自动生成一个名为"airflow_monitoring"的DAG?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

在GCP Composer上创建Airflow环境时，会自动创建一个名为airflow_monitoring的DAG，即使删除该DAG也会返回.

When creating an Airflow environment on GCP Composer, there is a DAG named airflow_monitoring automatically created and that comes back even when deleted.

为什么?怎么处理呢?我是否应该将此文件复制到DAG文件夹中，然后辞职以使其成为代码的一部分?我注意到，每次上载代码时，它都会停止执行该DAG，因为在DAG文件夹中找不到该DAG之前，它神奇地重新出现了.

Why? How to handle it? Should I copy this file inside my DAG folder and resign myself to make it part of my code? I noticed that each time I upload my code it stops the execution of this DAG as it could not be found inside the DAG folder until it magically reappears.

我已经尝试过在DAG文件夹中删除它，删除日志，从UI中删除它，所有这些都同时进行，等等.

I have already tried deleting it inside the DAG folder, delete the logs, delete it from the UI, all of this at the same time etc.

推荐答案

airflow_monitoring DAG是针对每个环境的活动探测器/运行状况检查，用于填充Cloud Composer监视指标environment/healthy.它是环境总体健康状况的指标，或更具体地说，它是调度DAG和运行任务的能力的指标.这样一来，您就可以使用Google Cloud Monitoring功能(例如指标图)，或者在环境变得不健康时设置警报.

The airflow_monitoring DAG is a per-environment liveness prober/healthcheck that is used to populate the Cloud Composer monitoring metric environment/healthy. It is an indicator for the general overall health of your environment, or more specifically, its ability to schedule DAGs and run tasks. This allows you to use Google Cloud Monitoring features such as metric graphs, or setting alerts when your environment becomes unhealthy.

您可以在 GCP指标列表，并可以在以下位置的云监控中浏览指标:

You can find more information about the metric on the GCP Metrics List, and can explore the metric in Cloud Monitoring under the following:

• 资源类型:Cloud Composer环境
• 指标:健康

这是由Composer管理的DAG，它使用您环境中的资源非常少.理想情况下，应保持不变，因为它对环境中运行的其他任何东西几乎没有影响.

This is a Composer-managed DAG and uses very minimal resources from your environment. Ideally, you should leave it untouched, as it has little to no effect on anything else running in your environment.