[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-29。"],[[["\u003cp\u003eThis page explains how to access and utilize the Cloud Composer monitoring dashboard to track DAG runs, identify issues with Airflow components, and monitor resource usage within a specific environment.\u003c/p\u003e\n"],["\u003cp\u003eThe monitoring dashboard provides various metrics, charts, and timelines, such as environment health, DAG statistics, scheduler details, worker performance, triggerer activity, web server status, and SQL database information, to assess the state and performance of the Cloud Composer environment.\u003c/p\u003e\n"],["\u003cp\u003eYou can set up alerts directly from the monitoring dashboard for specific metrics to receive notifications about potential issues, and view in Metrics Explorer for a closer look at a metric.\u003c/p\u003e\n"],["\u003cp\u003eThe page differentiates between DAG parse time, which is the time for the Airflow scheduler to read and process a DAG file, and DAG execution time, which is the total duration of task executions within a DAG.\u003c/p\u003e\n"],["\u003cp\u003eThe content on this page is currently reflective of Cloud Composer 2, and is yet to be updated for Cloud Composer 3.\u003c/p\u003e\n"]]],[],null,["# Use the monitoring dashboard\n\n**Cloud Composer 3** \\| [Cloud Composer 2](/composer/docs/composer-2/use-monitoring-dashboard \"View this page for Cloud Composer 2\") \\| [Cloud Composer 1](/composer/docs/composer-1/use-monitoring-dashboard \"View this page for Cloud Composer 1\")\n\n\u003cbr /\u003e\n\n| **Note:** This page is **not yet revised for Cloud Composer 3** and displays content for Cloud Composer 2.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes how to access and use the monitoring dashboard for a\nCloud Composer environment.\n\n- For a tutorial on monitoring key environment metrics, see\n [Monitor environment health and performance with key metrics](/composer/docs/composer-2/monitor-key-metrics).\n\n- For more information about specific metrics, see\n [Monitor environments with Cloud Monitoring](/composer/docs/composer-2/monitor-environments).\n\nAccess the monitoring dashboard\n-------------------------------\n\nThe monitoring dashboard contains metrics and charts for monitoring trends in\nthe DAG runs in your environment, and identifing issues with Airflow\ncomponents and Cloud Composer resources.\n\nTo access the monitoring dashboard for your environment:\n\n1. In the Google Cloud console, go to the **Environments** page.\n\n [Go to Environments](https://console.cloud.google.com/composer/environments)\n2. In the list of environments, click the name of your environment.\n The **Environment details** page opens.\n\n3. Go to the **Monitoring** tab.\n\nSet up alerts for metrics\n-------------------------\n\nYou can set up alerts for a metric by clicking the bell icon in the corner of\nthe monitoring card.\n[](/static/composer/docs/images/monitoring-dashboard-alert.png) **Figure 1.** Create an alert for a metric displayed on the monitoring dashboard (click to enlarge)\n\nView a metric in Monitoring\n---------------------------\n\nYou can get a closer look at a metric by viewing it in\nMonitoring.\n\nTo navigate there from the Cloud Composer monitoring dashboard, click\nthe three dots in the upper-right corner of a metric card and select\n**View in Metrics explorer**.\n[](/static/composer/docs/images/monitoring-view-metrics.png) **Figure 2.** View a metric from the monitoring dashboard in Metrics explorer (click to enlarge)\n\nMetric descriptions\n-------------------\n\nEach Cloud Composer environment has its own monitoring dashboard.\nMetrics displayed on a monitoring dashboard for a particular environment only\ntrack the DAG runs, Airflow components, and environment details for this\nenvironment only. For example, if you have two environments, the dashboard\ndoes not aggregate metrics from both environments.\n\n### Environment overview\n\n### DAG statistics\n\n| **Note:** Follow the [DAG troubleshooting instructions](/composer/docs/composer-2/troubleshooting-dags) to diagnose DAG and task failures.\n\n### Scheduler statistics\n\n| **Note:** Follow the [scheduler troubleshooting instructions](/composer/docs/composer-2/troubleshooting-scheduling) to diagnose scheduling problems.\n\n### Worker statistics\n\n### Triggerer statistics\n\n### Web server statistics\n\n### SQL database statistics\n\n### Difference between DAG parse time and DAG execution time\n\nThe monitoring dashboard of an environment displays the total time\nrequired to parse all DAGs in your Cloud Composer environment and\nthe average time it takes to execute a DAG.\n\nParsing a DAG and scheduling tasks from a DAG for execution are two separate\noperations performed by the Airflow scheduler.\n[](/static/composer/docs/images/dag-parsing-task-execution.png) **Figure 3.** DAG parsing and task scheduling done by the Airflow scheduler (click to enlarge)\n\n*DAG parse time* is the amount of time it takes for the Airflow Scheduler to\nread a DAG file and parse it.\n\nBefore the Airflow scheduler can schedule any task from a DAG, the scheduler\nmust parse the DAG file to discover the structure of the DAG and defined\ntasks. After the DAG file is parsed, the scheduler can start scheduling\ntasks from the DAG.\n\n*DAG execution time* is the sum of all task execution times for a DAG.\n\nTo see how long it takes to execute a particular Airflow task from a DAG, in\nthe [Airflow web interface](/composer/docs/composer-2/access-airflow-web-interface), select a DAG and open the\n[**Task duration** tab](https://airflow.apache.org/docs/apache-airflow/stable/ui.html#task-duration). This tab displays task execution times\nfor the specified number of last DAG runs."]]