From a8b2ef869828023fe79c446a2c7f00e58208ec57 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:10:27 -0500 Subject: [PATCH 01/12] Update Kubernetes Airflow section to use Datadog Transport and add composite transport option - Add Option 1: Datadog Transport (recommended) with version requirements - Add Option 2: Composite Transport for multiple destinations - Add Option 3: Simple Configuration (backward compatible) - Specify version requirements: apache-airflow-providers-openlineage >= 1.11.0 and openlineage-python >= 1.23.0 for transport options --- content/en/data_jobs/airflow.md | 56 ++++++++++++++++++++++++++++----- 1 file changed, 48 insertions(+), 8 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 81b6218326603..58be8c83c87ec 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -46,7 +46,46 @@ To get started, follow the instructions below. openlineage-airflow ``` -2. Configure `openlineage` provider. The simplest option is to set the following environment variables and make them available to pods where you run Airflow schedulers and Airflow workers: +2. Configure `openlineage` provider. Choose one of the following configuration options and set the environment variables, making them available to pods where you run Airflow schedulers and Airflow workers: + + **Option 1: Datadog Transport (Recommended)** + + **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.23.0 or later. + + ```shell + export OPENLINEAGE__TRANSPORT__TYPE=datadog + export OPENLINEAGE__TRANSPORT__URL= + export OPENLINEAGE__TRANSPORT__AUTH__TYPE=api_key + export OPENLINEAGE__TRANSPORT__AUTH__API_KEY= + export OPENLINEAGE__TRANSPORT__COMPRESSION=gzip + # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value + export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} + ``` + * Replace `` with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. + * Replace `` with your valid [Datadog API key][4]. + + **Option 2: Composite Transport** + + **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.23.0 or later. + + Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): + + ```shell + export OPENLINEAGE__TRANSPORT__TYPE=composite + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=http + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__URL= + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__AUTH__TYPE=api_key + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__AUTH__API_KEY= + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__COMPRESSION=gzip + # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value + export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} + ``` + * Replace `` with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. + * Replace `` with your valid [Datadog API key][4]. + + **Option 3: Simple Configuration** + + This option uses the simple URL-based configuration and works with all versions of the OpenLineage provider: ```shell export OPENLINEAGE_URL= @@ -56,6 +95,7 @@ To get started, follow the instructions below. ``` * Replace `` with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. * Replace `` with your valid [Datadog API key][4]. + * If you're using **Airflow v2.7 or v2.8**, also add these two environment variables along with the previous ones. This fixes an OpenLinage config issue fixed at `apache-airflow-providers-openlineage` v1.7, while Airflow v2.7 and v2.8 use previous versions. ```shell #!/bin/sh @@ -68,7 +108,7 @@ To get started, follow the instructions below. 3. Trigger an update to your Airflow pods and wait for them to finish. -4. Optionally, set up log collection for correlating task logs to DAG run executions in Data Jobs Monitoring. Correlation requires the logs directory to follow the [default log filename format][6]. +4. Optionally, set up log collection for correlating task logs to DAG run executions in Data Jobs Monitoring. Correlation requires the logs directory to follow the [default log filename format][6]. The `PATH_TO_AIRFLOW_LOGS` value is `$AIRFLOW_HOME/logs` in standard deployments, but may differ if customized. Add the following annotation to your pod: ```yaml @@ -76,13 +116,13 @@ To get started, follow the instructions below. ``` Adding `"source": "airflow"` enables the extraction of the correlation-required attributes by the [Airflow integration][8] logs pipeline. - + These file paths are relative to the Agent container. Mount the directory containing the log file into both the application and Agent containers so the Agent can access it. For details, see [Collect logs from a container local log file][10]. **Note**: Log collection requires the Datadog agent to already be installed on your Kubernetes cluster. If you haven't installed it yet, see the [Kubernetes installation documentation][9]. For more methods to set up log collection on Kubernetes, see the [Kubernetes and Integrations configuration section][7]. - + [1]: https://github.com/apache/airflow/releases/tag/2.5.0 [2]: https://airflow.apache.org/docs/apache-airflow-providers-openlineage/stable/index.html @@ -270,10 +310,10 @@ To get started, follow the instructions below. ```text { - "type": "http", - "url": "", + "type": "http", + "url": "", "auth": { - "type": "api_key", + "type": "api_key", "api_key": "" } } @@ -281,7 +321,7 @@ To get started, follow the instructions below. * Replace `` fully with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. * Replace `` fully with your valid [Datadog API key][5]. - + Check official [Airflow][4] and [Composer][3] documentation pages for other supported configurations of the `openlineage` provider in Google Cloud Composer. From cf7d17d5913584255d00d40ad77f057e6353c47f Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:13:12 -0500 Subject: [PATCH 02/12] Update openlineage-python version requirement to 1.37.0+ --- content/en/data_jobs/airflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 58be8c83c87ec..a6f989d85f022 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -50,7 +50,7 @@ To get started, follow the instructions below. **Option 1: Datadog Transport (Recommended)** - **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.23.0 or later. + **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. ```shell export OPENLINEAGE__TRANSPORT__TYPE=datadog @@ -66,7 +66,7 @@ To get started, follow the instructions below. **Option 2: Composite Transport** - **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.23.0 or later. + **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): From acdbd325d0edca51fe97dc7b9c6385657d6d8606 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:14:56 -0500 Subject: [PATCH 03/12] Update apache-airflow-providers-openlineage version requirement to 2.7.3+ --- content/en/data_jobs/airflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index a6f989d85f022..db2c9607a5de5 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -50,7 +50,7 @@ To get started, follow the instructions below. **Option 1: Datadog Transport (Recommended)** - **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. + **Requirements**: Requires `apache-airflow-providers-openlineage` version 2.7.3 or later and `openlineage-python` version 1.37.0 or later. ```shell export OPENLINEAGE__TRANSPORT__TYPE=datadog @@ -66,7 +66,7 @@ To get started, follow the instructions below. **Option 2: Composite Transport** - **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. + **Requirements**: Requires `apache-airflow-providers-openlineage` version 2.7.3 or later and `openlineage-python` version 1.37.0 or later. Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): From 92f7cae0c1d8c896fedaf41d7be92cd518aae19e Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:15:40 -0500 Subject: [PATCH 04/12] Update composite transport version requirement to 1.11.0+ --- content/en/data_jobs/airflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index db2c9607a5de5..142bb020a41fb 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -66,7 +66,7 @@ To get started, follow the instructions below. **Option 2: Composite Transport** - **Requirements**: Requires `apache-airflow-providers-openlineage` version 2.7.3 or later and `openlineage-python` version 1.37.0 or later. + **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): From 7d28343db1e7ec51011278eb07cccac8985d9d2e Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:17:22 -0500 Subject: [PATCH 05/12] Simplify Datadog Transport configuration to use DD_API_KEY and DD_SITE --- content/en/data_jobs/airflow.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 142bb020a41fb..d7c10c5a5c46c 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -53,16 +53,12 @@ To get started, follow the instructions below. **Requirements**: Requires `apache-airflow-providers-openlineage` version 2.7.3 or later and `openlineage-python` version 1.37.0 or later. ```shell + export DD_API_KEY= + export DD_SITE= export OPENLINEAGE__TRANSPORT__TYPE=datadog - export OPENLINEAGE__TRANSPORT__URL= - export OPENLINEAGE__TRANSPORT__AUTH__TYPE=api_key - export OPENLINEAGE__TRANSPORT__AUTH__API_KEY= - export OPENLINEAGE__TRANSPORT__COMPRESSION=gzip - # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value - export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` - * Replace `` with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. * Replace `` with your valid [Datadog API key][4]. + * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). **Option 2: Composite Transport** From 087ef1905fd2d2368ef509bf8f912d2f9c73d8f2 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:17:58 -0500 Subject: [PATCH 06/12] Add OPENLINEAGE_NAMESPACE back to Datadog Transport configuration --- content/en/data_jobs/airflow.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index d7c10c5a5c46c..ab2711eb22e5d 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -56,6 +56,8 @@ To get started, follow the instructions below. export DD_API_KEY= export DD_SITE= export OPENLINEAGE__TRANSPORT__TYPE=datadog + # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value + export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` * Replace `` with your valid [Datadog API key][4]. * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). From a19458827bb8cfc094ec3c23d7ff6936049d1275 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:18:22 -0500 Subject: [PATCH 07/12] Simplify composite transport configuration to use DD_API_KEY and DD_SITE --- content/en/data_jobs/airflow.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index ab2711eb22e5d..93e8e8216324e 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -69,17 +69,15 @@ To get started, follow the instructions below. Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): ```shell + export DD_API_KEY= + export DD_SITE= export OPENLINEAGE__TRANSPORT__TYPE=composite - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=http - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__URL= - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__AUTH__TYPE=api_key - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__AUTH__API_KEY= - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__COMPRESSION=gzip + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=datadog # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` - * Replace `` with `https://data-obs-intake.`{{< region-param key="dd_site" code="true" >}}. * Replace `` with your valid [Datadog API key][4]. + * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). **Option 3: Simple Configuration** From d62d4cf49dfa5f1eed6648590b988b65bbc14838 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:19:32 -0500 Subject: [PATCH 08/12] Add section explaining how to keep existing OpenLineage configuration with composite transport --- content/en/data_jobs/airflow.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 93e8e8216324e..d5e4eb92f6b5b 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -79,6 +79,29 @@ To get started, follow the instructions below. * Replace `` with your valid [Datadog API key][4]. * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). + **Keeping your existing OpenLineage configuration** + + If you're already using OpenLineage with another system (for example, with a standard HTTP transport), you can keep your existing configuration and add Datadog as an additional destination. The composite transport sends events to all configured transports. + + For example, if you're currently using an HTTP transport to send events to another system: + + ```shell + # Your existing HTTP transport configuration + export OPENLINEAGE__TRANSPORT__TYPE=composite + export OPENLINEAGE__TRANSPORT__TRANSPORTS__EXISTING__TYPE=http + export OPENLINEAGE__TRANSPORT__TRANSPORTS__EXISTING__URL= + export OPENLINEAGE__TRANSPORT__TRANSPORTS__EXISTING__AUTH__TYPE=api_key + export OPENLINEAGE__TRANSPORT__TRANSPORTS__EXISTING__AUTH__API_KEY= + + # Add Datadog as an additional transport + export DD_API_KEY= + export DD_SITE= + export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=datadog + export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} + ``` + + In this example, OpenLineage events are sent to both your existing system and Datadog. You can configure multiple transports by giving each one a unique name (like `EXISTING` and `DATADOG` in the example above). + **Option 3: Simple Configuration** This option uses the simple URL-based configuration and works with all versions of the OpenLineage provider: From 63945e6bd14c28a30f0477ad100ffde78064ff86 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 15:21:28 -0500 Subject: [PATCH 09/12] Refactor composite transport section to focus on existing OpenLineage transport use case --- content/en/data_jobs/airflow.md | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index d5e4eb92f6b5b..9ef49fce0be70 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -66,22 +66,7 @@ To get started, follow the instructions below. **Requirements**: Requires `apache-airflow-providers-openlineage` version 1.11.0 or later and `openlineage-python` version 1.37.0 or later. - Use this option if you need to send OpenLineage events to multiple destinations (for example, if you're already using OpenLineage with another system and want to add Datadog as an additional destination): - - ```shell - export DD_API_KEY= - export DD_SITE= - export OPENLINEAGE__TRANSPORT__TYPE=composite - export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=datadog - # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value - export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} - ``` - * Replace `` with your valid [Datadog API key][4]. - * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). - - **Keeping your existing OpenLineage configuration** - - If you're already using OpenLineage with another system (for example, with a standard HTTP transport), you can keep your existing configuration and add Datadog as an additional destination. The composite transport sends events to all configured transports. + Use this option if you're already using OpenLineage with another system and want to add Datadog as an additional destination. The composite transport sends events to all configured transports. For example, if you're currently using an HTTP transport to send events to another system: @@ -97,8 +82,12 @@ To get started, follow the instructions below. export DD_API_KEY= export DD_SITE= export OPENLINEAGE__TRANSPORT__TRANSPORTS__DATADOG__TYPE=datadog + # OPENLINEAGE_NAMESPACE sets the 'env' tag value in Datadog. You can hardcode this to a different value export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` + * Replace `` with your valid [Datadog API key][4]. + * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). + * Replace `` and `` with your existing OpenLineage transport configuration. In this example, OpenLineage events are sent to both your existing system and Datadog. You can configure multiple transports by giving each one a unique name (like `EXISTING` and `DATADOG` in the example above). From 6956000800dc2e5dec44c7e7967ad33cb87a8bb5 Mon Sep 17 00:00:00 2001 From: cecilia saixue watt Date: Tue, 11 Nov 2025 14:23:21 -0800 Subject: [PATCH 10/12] add region-dependent shortcodes --- content/en/data_jobs/airflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 9ef49fce0be70..6c79ec6ed1a21 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -60,7 +60,7 @@ To get started, follow the instructions below. export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` * Replace `` with your valid [Datadog API key][4]. - * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). + * Replace `` with your Datadog site (for example, {{< region-param key="dd_site" code="true" >}}). **Option 2: Composite Transport** @@ -86,7 +86,7 @@ To get started, follow the instructions below. export OPENLINEAGE_NAMESPACE=${AIRFLOW_ENV_NAME} ``` * Replace `` with your valid [Datadog API key][4]. - * Replace `` with your Datadog site (for example, `datadoghq.com`, `datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ddog-gov.com`). + * Replace `` with your Datadog site (for example, {{< region-param key="dd_site" code="true" >}}). * Replace `` and `` with your existing OpenLineage transport configuration. In this example, OpenLineage events are sent to both your existing system and Datadog. You can configure multiple transports by giving each one a unique name (like `EXISTING` and `DATADOG` in the example above). From 981e85150c0182846ade0831f84659bd7e07e584 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 17:59:06 -0500 Subject: [PATCH 11/12] Update airflow.md Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> --- content/en/data_jobs/airflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 6c79ec6ed1a21..5b4903cbd3e40 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -93,7 +93,7 @@ To get started, follow the instructions below. **Option 3: Simple Configuration** - This option uses the simple URL-based configuration and works with all versions of the OpenLineage provider: + This option uses the URL-based configuration and works with all versions of the OpenLineage provider: ```shell export OPENLINEAGE_URL= From dac6748158cde4ff9431dd7997c32a826c0f6556 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 11 Nov 2025 17:59:15 -0500 Subject: [PATCH 12/12] Update airflow.md Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> --- content/en/data_jobs/airflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/airflow.md b/content/en/data_jobs/airflow.md index 5b4903cbd3e40..b71aeb6dfbb85 100644 --- a/content/en/data_jobs/airflow.md +++ b/content/en/data_jobs/airflow.md @@ -68,7 +68,7 @@ To get started, follow the instructions below. Use this option if you're already using OpenLineage with another system and want to add Datadog as an additional destination. The composite transport sends events to all configured transports. - For example, if you're currently using an HTTP transport to send events to another system: + For example, if you're using an HTTP transport to send events to another system: ```shell # Your existing HTTP transport configuration