Automated Astronomer Pipeline Trend Reports
Every Monday, WebRun signs into Astronomer, opens each deployment, reviews last week's DAG runs for success rate, average duration, and retries, appends one row per DAG to an Airtable history, compares against the previous weeks, and opens a Trello card for any pipeline whose run time or failure rate is trending the wrong way.
How do I spot Airflow pipelines that are getting slower over time?
WebRun reviews last week's DAG runs across your Astronomer deployments every Monday, capturing success rate, average duration, and retries for each pipeline. It appends the figures to an Airtable history, compares them with the four week average, and opens a Trello card for every pipeline trending slower or less reliable.
- Slow creep in DAG run time gets caught before it breaks an SLA
- Every pipeline has a dated performance history in Airtable
- Fix work lands on the board with the numbers already attached
Built for data engineers · analytics engineering teams · platform teams · data leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.astronomer.ioin a real browser with your saved login - no setup, no API keys. -
1
Astronomer - review last week's DAG runs
astronomer.io
WebRun opens Astronomer to review last week's DAG runs. - Sign into Astronomer and open each deployment on your watch list
- For every DAG, capture last week's run count, success and failure totals, average duration, and retry count
- Note any DAG that is paused, has no runs at all, or shows a growing queue
Done when Every DAG in every watched deployment has last week's figures.
-
2
Airtable - log run times and success rates
airtable.com
WebRun opens Airtable to log run times and success rates. - Open your pipeline history base and append one dated row per DAG
- Record deployment, DAG name, runs, success rate, average duration, and retries
- Compute the change in duration and success rate against the four week average
Done when Last week's figures are logged with a comparison to the four week average.
-
3
Trello - open a card for degrading pipelines
trello.com
WebRun opens Trello to open a card for degrading pipelines. - Open the data engineering board and create a card for each DAG that got materially slower or less reliable
- Put the deployment, the DAG name, and the before and after figures in the card description
- Skip DAGs that already have an open card and close cards where the trend has recovered
Done when Every degrading pipeline has a Trello card with its numbers.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it trigger, pause, or clear any DAG runs?
No. WebRun only reads run history in Astronomer. It never triggers a DAG, clears a task, pauses a schedule, or changes deployment settings.
How does it decide a pipeline is degrading?
It compares last week's average duration and success rate against the four week average already stored in Airtable, so a card is opened on a measured trend rather than one slow run.
Can it cover more than one deployment?
Yes. Give it the list of Astronomer deployments to watch and each run walks all of them, writing one Airtable row per DAG per deployment.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.