◆ Elasticsearch

Manage Elasticsearch data storage

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 Elasticsearch tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskDelete all log data older than 90 days from the 'application_logs_prod'…+
Delete all log data older than 90 days from the 'application_logs_prod' index.
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 we hit our storage limit on the 'customer_data' cluster, analyze the current data growth…+
Before we hit our storage limit on the 'customer_data' cluster, analyze the current data growth rate for the past six months. Project when we'll reach 90% capacity if the current trend continues, and suggest which indices have the highest potential for data lifecycle management optimization without losing critical audit trails.
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 'metrics' cluster just triggered a high disk usage alert, but I can't tell if it's a…+
Our 'metrics' cluster just triggered a high disk usage alert, but I can't tell if it's a temporary spike or a sustained growth issue.
Our 'metrics' cluster just triggered a high disk usage alert, but I can't tell if it's a temporary spike or a sustained growth issue. I'm afraid of running out of disk space before Monday, which would halt all new metric ingestion. I can't tell if the recent retention policy change for 'network_traffic_logs' actually took effect. What's the most likely reason for this sudden spike, and what's the fastest way to free up space without losing critical diagnostic data for the SRE team?
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 find myself scrambling to manage disk space and index sizes, often reacting to…+
I frequently find myself scrambling to manage disk space and index sizes, often reacting to alerts rather than planning.
I frequently find myself scrambling to manage disk space and index sizes, often reacting to alerts rather than planning. This leads to rushed decisions about data retention and potential data loss. What habit should I change to proactively manage our data storage, especially for high-volume log and metric indices, so I can ensure we always have enough capacity and clear retention policies in place before we hit critical thresholds?
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.