Running and scheduling pipelines
Last updated
Last updated
Ylem’s pipelines can be triggered in 5 different ways:
Both buttons to schedule or run the pipeline manually are located in the top right corner of the pipeline's canvas.
A manual trigger is typically used for:
Testing and debugging new pipelines or pipelines that stopped working as expected
Pipelines that don't have any periodical schedule, don't need to be triggered through the API but need to be run sometimes on demand when a user needs it
After clicking on the "Run pipeline" button a user gets an output that shows the status of every task or can open the full-text output log:
Scheduling is the most common way of triggering pipelines that need to do a periodical job. For example, reporting, and data preparation.
It can be configured using either a visual interface or if you are familiar with a cronjob format, you can also use this one.
For example, by Apache Airflow, Jenkins, or any other software that is already used in your company for workflow or pipeline orchestration.
More information about triggering pipelines via API can be found in the OAuth Clients and API Endpoints.
When placed as a first task in a pipeline, external_trigger allows you to trigger the pipeline from your data streaming platforms to make it 100% real-time.
More specific details can be found on the detailed pages for each integration:
In each metric, you can define which pipelines to execute depending on the value of your metric:
Some of the more detailed examples of metrics can be found in the list of our use cases. Our library of templates also contains multiple ones, which you can use for configuring your metrics.
