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

Feature Request: Add visualizer for tracking workflows and file inputs/outputs #1034

Open
lbeckman314 opened this issue Aug 14, 2024 · 0 comments

Comments

@lbeckman314
Copy link
Member

lbeckman314 commented Aug 14, 2024

Overview

Currently there is no visualizer for the workflows submitted in Funnel. It could be beneficial to add a way to allow users to track:

  • The history of workflows and whether they succeeded or failed
  • Location of the workflow inputs and outputs
  • The declarative workflow definition files themselves

Dagu

One possible option for implementing this feature would be to add the Golang program dagu as an extension to Funnel:

Dagu is a powerful Cron alternative that comes with a Web UI. It allows you to define dependencies between commands as a Directed Acyclic Graph (DAG) in a declarative YAML format. Dagu simplifies the management and execution of complex workflows. It natively supports running Docker containers, making HTTP requests, and executing commands over SSH.

Airflow

Alternatively a more established program like Apache Airflow could be used instead:

Apache Airflow (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.

When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative.

Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed.

Additional Resources

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

No branches or pull requests

1 participant