Skip to main content

View logs

View Airflow task and component logs to troubleshoot your data pipelines and better understand the behavior of your tasks and their execution environment.

View Airflow task logs

Airflow task logs for both local Airflow environments and Deployments on Astro are available in the Airflow UI. Task logs can help you troubleshoot a specific task instance that failed or retried.

  1. Access the Airflow UI. To access the Airflow UI for a Deployment, open the Deployment in the Cloud UI and click Open Airflow. To access the Airflow UI in a local environment, open a browser and go to http://localhost:8080.
  2. Click a DAG.
  3. Click Graph.
  4. Click a task run.
  5. Click Instance Details.
  6. Click Log.

On Astro, Airflow task logs are stored in the data plane on your cloud. On Amazon Web Services (AWS), they are stored in S3. On Google Cloud Platform (GCP), they are stored in Cloud Storage. Task logs are stored indefinitely for existing Astro clusters. The task log retention policy is not currently configurable.


Astro has early access support for forwarding Airflow task logs and basic Airflow metrics to Datadog. To enable log forwarding, submit a request to Astronomer Support.

In your request, make sure to provide your Datadog API key and identify on which Astro cluster(s) you want to enable the integration.

If you're interested in forwarding task logs to other third-party logging tools, also submit a request to Astronomer Support.

Access Airflow component logs locally

To show logs for your Airflow scheduler, webserver, or triggerer locally, run the following Astro CLI command:

astro dev logs

Once you run this command, the most recent logs for these components appear in your terminal window.

By default, running astro dev logs shows logs for all Airflow components. To see logs only for a specific component, add any of the following flags to your command:

  • --scheduler
  • --webserver
  • --triggerer

To continue monitoring logs, run astro dev logs --follow. The --follow flag ensures that the latest logs continue to appear in your terminal window. For more information about this command, see CLI Command Reference.

Logs for the Airflow webserver, worker, and triggerer are not available for Deployments on Astro.

View Airflow scheduler logs

You can access the past 24 hours of scheduler logs for any Astro Deployment on the Scheduler Logs page of the Cloud UI. Logs are color-coded according to their type. Scheduler logs can help you understand scheduler performance and indicate if a task failed due to an issue with the scheduler. For more information on configuring the scheduler on Astro, see Scheduler resources.

  1. In the Cloud UI, select a Workspace.

  2. Click Logs on the left-hand menu.

    Logs icon and button

  3. Select a Deployment in the Select a Deployment menu.

  4. Optional. Select one or more options in the Log Level menu and click Apply. These are the available options:

    • Error: Emitted when a process fails or does not complete. For example, these logs might indicate a missing DAG file, an issue with your scheduler's connection to the Airflow database, or an irregularity with your scheduler's heartbeat.
    • Warn: Emitted when Airflow detects an issue that may or may not be of concern but does not require immediate action. This often includes deprecation notices marked as DeprecationWarning. For example, Airflow might recommend that you upgrade your Deployment if there was a change to the Airflow database or task execution logic.
    • Info: Emitted frequently by Airflow to show that a standard scheduler process, such as DAG parsing, has started. These logs are frequent but can contain useful information. If you run dynamically generated DAGs, for example, these logs will show how many DAGs were created per DAG file and how long it took the scheduler to parse each of them.
  5. Optional. To view the scheduler logs for another Deployment, select a different Deployment in the Select a Deployment menu.

When a Deployment generates more than 500 lines of logs in 24 hours, only the most recent 500 lines are shown. If there are no scheduler logs available for a given Deployment, you will see:

No matching events have been recorded in the past 24 hours.

This likely indicates that the Deployment you selected does not currently have any DAGs running.