Data pipeline management
Setup
If you haven’t setup a project before, check out the setup guide before starting.
Pipelines
http://localhost:3000/pipelines
This page will show all the pipelines in your project.
Core abstraction: Pipeline
A pipeline contains references to all the blocks of code you want to run, charts for visualizing data, and organizes the dependency between each block of code.
Learn more about projects and pipelines here.
From this page, you can also create a new pipeline by clicking the
[+ New pipeline] button.
Creating new pipeline
Creating a new pipeline will take you to the Pipeline edit page; a notebook-like experience for adding blocks, creating dependencies between blocks, testing code, and visualizing data with charts.
Learn more about the Notebook for building data pipelines
Pipeline runs
http://localhost:3000/pipeline-runs
View all the runs for every pipeline in your current project.
Core abstraction: Run
A run record stores information about when it was started, its status, when it was completed, any runtime variables used in the execution of the pipeline or block, etc.
Pipeline detail
http://localhost:3000/pipelines/[uuid]
This page contains all the information and history for a single pipeline:
Triggers
http://localhost:3000/pipelines/example_pipeline/triggers
This page shows all the active and inactive triggers for a single pipeline.
Core abstraction: Trigger
A trigger is a set of instructions that determine when or how a pipeline should run.
Create trigger
http://localhost:3000/pipelines/[uuid]/triggers/[id]/edit
Create a new trigger for this pipeline by clicking the [+ Create] button
near the top of the page.
You can configure the trigger to run the pipeline on a schedule, when an event occurs, or when an API is called.
Core abstraction: Schedule
A schedule type trigger will instruct the pipeline to run after a start date and on a set interval.
Core abstraction: Event
An event type trigger will instruct the pipeline to run whenever a specific event occurs.
Core abstraction: API
An API trigger will instruct the pipeline to run whenever a specific API is called.
Trigger detail
On this page, you can start or pause the trigger. Starting the trigger will make it active. Pausing the trigger will prevent it from running the pipeline.
If you have other triggers for this pipeline, pausing 1 trigger may not stop the pipeline from running since other triggers can also run the pipeline.
You can also edit the trigger after creating it by clicking the
[Edit trigger] button.
Runs
http://localhost:3000/pipelines/example_pipeline/runs
View the pipeline runs and block runs for a pipeline.
Core abstraction: Run
A run record stores information about when it was started, its status, when it was completed, any runtime variables used in the execution of the pipeline or block, etc.
Retry run
WIP
Logs
http://localhost:3000/pipelines/example_pipeline/logs
Browse all logs for a pipeline. You can search and filter logs by log level, block type, block UUID, and more.
Core abstraction: Log
A log is a file that contains system output information.
Backfill
WIP
Monitor
You can monitor many metrics for each of your pipelines and blocks. Soon, you’ll be able to monitor aggregate metrics across all pipelines and blocks.
Read more here.
Concurrency
You can limit the concurrency of the block execution to reduce resource consumption.
You can configure the maximum number of concurrent block runs in project’s metadata.yaml via queue_config.
queue_config:
concurrency: 100
The default value of concurrency is 20.