为什么在GCP Composer中会自动生成DAG'airflow_monitoring'？ [英] Why is there an automatic DAG 'airflow_monitoring' generated in GCP Composer?

问题描述

在GCP Composer上创建Airflow环境时，会自动创建一个名为 airflow_monitoring的DAG，并且无法删除。为什么呢
如何处理？我是否应该将此文件复制到DAG文件夹中，然后辞职以使其成为代码的一部分？我注意到，每次我上载代码时，它都会停止执行该DAG，因为在DAG文件夹中找不到它，除非它神奇地重新出现为止。

When creating an Airflow environment on GCP Composer, there is a DAG named "airflow_monitoring" automatically created and that is impossible to delete. 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监视指标环境/健康。它检查环境的总体总体运行状况，或更具体地说，检查其功能计划DAG。这样一来，您就可以使用Stackdriver功能（例如度量标准图表），或者在环境不健康时设置警报。

The airflow_monitoring DAG is a per-environment liveness prober/healthcheck that is used to populate the Cloud Composer monitoring metric environment/healthy. It checks for the general overall health of your environment, or more specifically its ability schedule DAGs. This allows you to use Stackdriver 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 Stackdriver Monitoring under the following:

• 资源类型：Cloud Composer环境


• 指标：健康

这是由Composer管理的DAG并且使用您环境中的资源极少。理想情况下，您应该将其保留在DAGs文件夹中。

This is a Composer-managed DAG and uses very minimal resources from your environment. Ideally, you should just leave it in your DAGs folder.

这篇关于为什么在GCP Composer中会自动生成DAG'airflow_monitoring'？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！