Create DAG documentation in Apache Airflow

Info

This page has not yet been updated for Airflow 3. The concepts shown are relevant, but some code may need to be updated. If you run any examples, take care to update import statements and watch for any other breaking changes.

One of the more powerful and lesser-known features of Airflow is that you can create Markdown-based DAG documentation that appears in the Airflow UI

After you complete this tutorial, you’ll be able to:

• Add custom doc strings to an Airflow DAG.
• Add custom doc strings to an Airflow task.

Time to complete

This tutorial takes approximately 15 minutes to complete.

Assumed knowledge

• Basic Airflow concepts. See Introduction to Apache Airflow.
• Basic Python. See the Python Documentation.

Prerequisites

• The Astro CLI.

Step 1: Create an Astro project

To run Airflow locally, you first need to create an Astro project.

1. Create a new directory for your Astro project:

   1
   mkdir <your-astro-project-name> && cd <your-astro-project-name>

2. Run the following Astro CLI command to initialize an Astro project in the directory:

   1
   astro dev init

3. To enable raw HTML in your Markdown DAG descriptions, add the following Airflow config environment variable to your .env file. This will allow you to use HTML in your DAG descriptions. If you don’t want to enable this setting due to security concerns you will still be able to use Markdown in your DAG descriptions and the HTML shown in this tutorial will be displayed as raw content.

   AIRFLOW__WEBSERVER__ALLOW_RAW_HTML_DESCRIPTIONS=True

4. Start your Airflow instance by running:

   1
   astro dev start

Step 2: Create a new DAG

1. In your dags folder, create a file named docs_example_dag.py.

2. Copy and paste one of the following DAGs based on which coding style you’re most comfortable with.

1
from airflow.decorators import task, dag
2
from pendulum import datetime
3
import requests
4
5
@dag(
6
    start_date=datetime(2022,11,1),
7
    schedule="@daily",
8
    catchup=False
9
)
10
def docs_example_dag():
11
12
    @task
13
    def tell_me_what_to_do():
14
        response = requests.get("https://bored-api.appbrewery.com/random")
15
        return response.json()["activity"]
16
17
    tell_me_what_to_do()
18
19
docs_example_dag()

1
from airflow.models.dag import DAG
2
from airflow.operators.python import PythonOperator
3
from pendulum import datetime
4
import requests
5
6
def query_api():
7
    response = requests.get("https://bored-api.appbrewery.com/random")
8
    return response.json()["activity"]
9
10
with DAG(
11
    dag_id="docs_example_dag",
12
    start_date=datetime(2022,11,1),
13
    schedule=None,
14
    catchup=False,
15
):
16
17
    tell_me_what_to_do = PythonOperator(
18
        task_id="tell_me_what_to_do",
19
        python_callable=query_api,
20
    )

This DAG has one task called tell_me_what_to_do, which queries an API that provides a random activity for the day and prints it to the logs.

Step 3: Add docs to your DAG

You can add Markdown-based documentation to your DAGs that will render in the Grid, Graph and Calendar pages of the Airflow UI.

1. In your docs_example_dag.py file, add the following doc string above the definition of your DAG:

   1
   doc_md_DAG = """
   2
   ### The Activity DAG
   3
   4
   This DAG will help me decide what to do today. It uses the [BoredAPI](https://bored-api.appbrewery.com/random) to do so.
   5
   6
   Before I get to do the activity I will have to:
   7
   8
   - Clean up the kitchen.
   9
   - Check on my pipelines.
   10
   - Water the plants.
   11
   12
   Here are some happy plants:
   13
   14
   <img src="https://www.publicdomainpictures.net/pictures/80000/velka/succulent-roses-echeveria.jpg" alt="plants" width="300"/>
   15
   """

   This doc string is written in Markdown. It includes a title, a link to an external website, a bulleted list, as well as an image which has been formatted using HTML. To learn more about Markdown, see The Markdown Guide.

2. Add the documentation to your DAG by passing doc_md_DAG to the doc_md parameter of your DAG class as shown in the code snippet below:

1
@dag(
2
    start_date=datetime(2022,11,1),
3
    schedule="@daily",
4
    catchup=False,
5
    doc_md=doc_md_DAG
6
)
7
def docs_example_dag():

1
with DAG(
2
    dag_id="docs_example_dag",
3
    start_date=datetime(2022,11,1),
4
    schedule="@daily",
5
    catchup=False,
6
    doc_md=doc_md_DAG
7
):

3. Go to the Grid view and click on the DAG Docs banner to view the rendered documentation.

   

Tip

Airflow will automatically pick up a doc string written directly beneath the definition of the DAG context and add it as DAG Docs. Additionally, using with DAG(): lets you pass the filepath of a markdown file to the doc_md parameter. This can be useful if you want to add the same documentation to several of your DAGs.

Step 4: Add docs to a task

You can also add docs to specific Airflow tasks using Markdown, Monospace, JSON, YAML or reStructuredText. Note that only Markdown will be rendered and other formats will be displayed as rich content.

To add documentation to your task, follow these steps:

1. Add the following code with a string in Markdown format:

   1
   doc_md_task = """
   2
   3
   ### Purpose of this task
   4
   5
   This task **boldly** suggests a daily activity.
   6
   """

2. Add the following code with a string written in monospace format:

   1
   doc_monospace_task = """
   2
   If you don't like the suggested activity you can always just go to the park instead.
   3
   """

3. Add the following code with a string in JSON format:

   1
   doc_json_task = """
   2
   {
   3
       "previous_suggestions": {
   4
           "go to the gym": ["frequency": 2, "rating": 8],
   5
           "mow your lawn": ["frequency": 1, "rating": 2],
   6
           "read a book": ["frequency": 3, "rating": 10],
   7
       }
   8
   }
   9
   """

4. Add the following code with a string written in YAML format:

   1
   doc_yaml_task = """
   2
   clothes_to_wear: sports
   3
   gear: |
   4
       - climbing: true
   5
       - swimming: false
   6
   """

5. Add the following code containing reStructuredText:

   1
   doc_rst_task = """
   2
   ===========
   3
   This feature is pretty neat
   4
   ===========
   5
   6
   * there are many ways to add docs
   7
   * luckily Airflow supports a lot of them
   8
   9
   .. note:: `Learn more about rst here! <https://gdal.org/contributing/rst_style.html#>`__
   10
   """

6. Create a task definition as shown in the following snippet. The task definition includes parameters for specifying each of the documentation strings you created. Pick the coding style you’re most comfortable with.

1
@task(
2
    doc_md=doc_md_task,
3
    doc=doc_monospace_task,
4
    doc_json=doc_json_task,
5
    doc_yaml=doc_yaml_task,
6
    doc_rst=doc_rst_task
7
)
8
def tell_me_what_to_do():
9
    response = requests.get("https://bored-api.appbrewery.com/random")
10
    return response.json()["activity"]
11
12
tell_me_what_to_do()

1
tell_me_what_to_do = PythonOperator(
2
    task_id="tell_me_what_to_do",
3
    python_callable=query_api,
4
    doc_md=doc_md_task,
5
    doc=doc_monospace_task,
6
    doc_json=doc_json_task,
7
    doc_yaml=doc_yaml_task,
8
    doc_rst=doc_rst_task
9
)

3. Go to the Airflow UI and run your DAG.

4. In the Grid view, click on the green square for your task instance.

5. Click on Task Instance Details.

   

6. See the docs under their respective attribute:

   

In Airflow 2.10+, task docs provided to doc_md or as a doc string in a @task decorated task are rendered in the task details in the Airflow UI.

Step 5: Add notes to a task instance and DAG run

You can add notes to task instances and DAG runs from the Grid view in the Airflow UI. This feature is useful if you need to share contextual information about a DAG or task run with your team, such as why a specific run failed.

1. Go to the Grid View of the docs_example_dag DAG you created in Step 2.

2. Select a task instance or DAG run.

3. Click Details > Task Instance Notes or DAG Run notes > Add Note.

4. Write a note and click Save Note.

Conclusion

Congratulations! You now know how to add fancy documentation to both your DAGs and your Airflow tasks.