This guide will show you how to securely connect SYNQ to your Airflow setup.We need this information so we can extract metadata about Airflow. By default, all tasks and all DAGs will be reported to us.To be able to finish this guide, you’ll need the following:
→ Access to modify your Airflow configuration code⏱️ Estimated time to finish: 10 minutes.
→ Access to modify your Airflow configuration code⏱️ Estimated time to finish: 10 minutes.
Setup
- Install the required dependencies in your Airflow
- Setup the REST hook
conn-host
:https://datahubapi.synq.io/datahub/v1/
conn-password
: Token from SYNQ you obtain when you click ‘Create’ on this page
Airflow 2.7+ with OpenLineage Provider
If you’re using Airflow 2.7+, the native Airflow OpenLineage provider will improve the quality of lineage and metadata information obtained from your Airflow setup. The OpenLineage provider package is already included in the installation above since the DataHub plugin requires it. For AWS MWAA, add bothacryl-datahub-airflow-plugin
and apache-airflow-providers-openlineage
to your requirements.txt
file.
Note: Native OpenLineage support is planned for SYNQ. Currently, the DataHub plugin is required to collect Airflow metadata.
Log Forwarding
Log forwarding is required to include task failure snippets in SYNQ alerts. SYNQ supports multiple methods for forwarding Airflow logs:AWS MWAA CloudWatch Logs
For AWS Managed Workflows for Apache Airflow (MWAA), you can forward logs from CloudWatch using thesynq-aws-cloudwatch
Lambda function:
- Deploy the Lambda function: Use the synq-aws-cloudwatch repository to deploy a Lambda function that forwards CloudWatch logs to SYNQ.
- Configure log forwarding: The Lambda automatically forwards Airflow logs from CloudWatch to SYNQ when properly configured with your SYNQ credentials.
- Set up log group subscription: Configure CloudWatch to trigger the Lambda when new Airflow logs are available.