◆ Apache Airflow

Remove Airflow task logs

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe logs for the `etl_daily_load` DAG are filling up the disk. Clear out all logs older than 7…+
The logs for the `etl_daily_load` DAG are filling up the disk. Clear out all logs older than 7 days for that specific DAG.
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 acceptOur log storage costs are getting out of hand, especially for our high-frequency DAGs. Can we…+
Our log storage costs are getting out of hand, especially for our high-frequency DAGs. Can we implement a policy to automatically prune logs for all non-critical DAGs after 3 days, but keep critical financial data logs for 30 days, so we balance cost and compliance?
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 analytics server disk space is critically low, and the main dashboard isn't refreshing. I…+
The disk space on the analytics server is critically low, and I just got an alert that our main dashboard is not refreshing.
The analytics server disk space is critically low, and the main dashboard isn't refreshing. I suspect it's old logs, but I'm terrified of deleting something crucial for an audit. What's the safest way to quickly free up space without risking data integrity or compliance, and how can I prevent this from happening again on a Friday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly getting urgent alerts about disk space filling up, always due to excessive logs…+
I frequently get urgent alerts about disk space filling up, always due to excessive logs from various DAGs.
I'm constantly getting urgent alerts about disk space filling up, always due to excessive logs from various DAGs. This reactive scramble to clear space disrupts my focus and often delays other tasks. What habit can I change to proactively manage log retention across all our data pipelines, so I'm not always fighting fires?
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.