Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🔌 Provider]: Airflow Provider #4089

Open
tuantran0910 opened this issue Mar 18, 2025 · 3 comments · May be fixed by #4090
Open

[🔌 Provider]: Airflow Provider #4089

tuantran0910 opened this issue Mar 18, 2025 · 3 comments · May be fixed by #4090
Labels
Provider Providers related issues

Comments

@tuantran0910
Copy link

Apache Airflow is an open-source tool for programmatically authoring, scheduling, and monitoring data pipelines. Airflow's extensible Python framework enables you to build workflows that connect with virtually any technology.

When working with Airflow, it's essential to monitor the health of your DAGs and tasks to ensure that your data pipelines run smoothly. The Airflow Provider integration allows seamless communication between Airflow and Keep, so you can forward alerts, such as task failures, directly to Keep via webhook configurations.

The alerts will be centralized in Keep:

@tuantran0910 tuantran0910 added the Provider Providers related issues label Mar 18, 2025
@shahargl
Copy link
Member

Hey @tuantran0910, thanks for opening this issue!

Looking at your screenshot it seems you did some of the work - can you elaborate on how you got airflow alerts into Keep?

@tuantran0910
Copy link
Author

Hi @shahargl, I have forked the repo and did some of the work, I will push them and create the PR. I think there are some bugs and need the help of Keep's team :D Thanks

@tuantran0910 tuantran0910 linked a pull request Mar 18, 2025 that will close this issue
4 tasks
@talboren
Copy link
Member

👑👑👑

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Provider Providers related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants