◆ Elasticsearch

Find disk space usage

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 taskFind the current disk space usage for all data nodes in the production Elasticsearch cluster. I…+
Find the current disk space usage for all data nodes in the production Elasticsearch cluster. I need to see the total used, available, and percentage used for each node and for the cluster as a whole.
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 disk space, make it actionable for capacity planning. I need to see not just…+
Before I report on disk space, make it actionable for capacity planning. I need to see not just current usage, but also which indices are consuming the most space, and a projection of when we'll hit 90% capacity on the 'logs-01' node if current trends continue. Flag any nodes that are already above 80% usage.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentNode 'data-prod-03' just hit 95% disk utilization, and alerts are firing, but I can't…+
Disk space is critically low on a production Elasticsearch node, and I don't know why.
Node 'data-prod-03' just hit 95% disk utilization, and alerts are firing, but I can't immediately tell what's causing the spike. It wasn't this high yesterday. I'm afraid of the node going read-only and impacting critical logging services. Is it a sudden influx of new data into a specific index, or an issue with old data not being purged? What's the fastest way to identify the culprit index and free up space without deleting critical data?
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 always reacting to disk space alerts, scrambling to identify which indices are growing too…+
I'm constantly reacting to critical disk space alerts on Elasticsearch nodes.
I'm always reacting to disk space alerts, scrambling to identify which indices are growing too fast or which nodes are filling up. It feels like I'm playing whack-a-mole, and I constantly worry about hitting read-only blocks. I lose focus on proactive work. What habit can I change to anticipate disk space issues before they become critical, moving from reactive firefighting to proactive capacity management?
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.