◆ Elasticsearch

Troubleshoot low disk watermark exceeded

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 taskCheck the disk utilization for all nodes in the production cluster and tell me which ones are…+
Check the disk utilization for all nodes in the production cluster and tell me which ones are above the low watermark threshold.
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 I report on the low disk watermark issue, give me a breakdown of the disk usage per…+
Before I report on the low disk watermark issue, give me a breakdown of the disk usage per index on the affected nodes. Also, highlight any indices that are particularly large and haven't been recently optimized or cleared, so I can suggest immediate actions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur production cluster just hit the low disk watermark, and I'm getting alerts, but I can't…+
Our production cluster just hit the low disk watermark, and I'm getting alerts, but I can't find any obvious large indices to delete.
Our production cluster just hit the low disk watermark, and I'm getting alerts, but I can't find any obvious large indices to delete or shrink that would give us immediate relief. I'm afraid of data loss or performance degradation, and I can't just start deleting random data. What's the most likely reason I'm not seeing the culprit, and what's the safest, fastest way to free up space without impacting critical services?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently deal with low disk watermark alerts that interrupt my work, often because old logs…+
I frequently deal with low disk watermark alerts that interrupt my work.
I frequently deal with low disk watermark alerts that interrupt my work, often because old logs or temporary indices aren't cleaned up. What habit should I change to proactively manage disk space, like implementing better lifecycle policies or automated cleanup routines, so these alerts become rare rather than routine interruptions?
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 Elasticsearch'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.