◆ Apache Airflow

Set up Airflow monitoring dashboards

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up a new dashboard for the 'data_ingestion' team to monitor the status of their daily…+
Set up a new dashboard for the 'data_ingestion' team to monitor the status of their daily ingestion DAGs, showing success/failure rates and average task duration. It needs to be accessible via their existing monitoring tools by Friday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the Q4 peak, create a comprehensive monitoring dashboard for all critical production…+
Before the Q4 peak, create a comprehensive monitoring dashboard for all critical production DAGs. It needs to highlight any DAGs running longer than usual, tasks that have failed more than once in the last 24 hours, and overall resource utilization, so we can proactively identify bottlenecks.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe critical 'fraud_detection' DAG failed silently last night, and we only found out hours…+
The 'fraud_detection' DAG failed silently last night, and we only found out hours later from an angry business analyst.
The critical 'fraud_detection' DAG failed silently last night, and we only found out hours later when a business analyst called, furious about stale data. Our current dashboards didn't flag it. I'm worried about missing other critical failures. What's the quickest way to configure an alert for this specific DAG's failure that gets immediate attention, and what critical metric should I prioritize for immediate visibility?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternIt feels like we're always reacting to user complaints about stale data because our monitoring…+
We always find out about critical DAG failures from angry users, not our monitoring tools.
It feels like we're always reacting to user complaints about stale data because our monitoring doesn't catch critical DAG failures fast enough. This erodes trust with the business. What habit should I change in how we set up and review our monitoring dashboards to ensure we're the first to know about problems, not the last?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Airflow's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.