◆ Elasticsearch

Create snapshots

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 taskTake a full snapshot of the `production-data` index on Friday at 2 AM UTC and store it in the…+
Take a full snapshot of the `production-data` index on Friday at 2 AM UTC and store it in the `s3-backup-repository`. Retain this snapshot for 30 days.
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 quarterly compliance audit next month, review our snapshot strategy for the…+
Before the quarterly compliance audit next month, review our snapshot strategy for the `customer-records` index. We need to ensure we meet the 7-year retention requirement for daily snapshots and that the recovery process is well-documented. Suggest any changes or improvements needed to guarantee compliance and efficient restoration.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI need to restore a specific document from last Tuesday into the `qa-environment` for a bug…+
I need to restore a specific document from last Tuesday into the `qa-environment` for a bug reproduction, but I'm unsure which snapshot contains it.
I need to restore a specific document from last Tuesday into the `qa-environment` for a bug reproduction, but I'm unsure which snapshot contains it without restoring the entire index. I'm afraid of restoring the wrong data or overwriting something important in QA. I don't know the most efficient way to find the right snapshot and extract just that document. What's the most likely diagnosis for this uncertainty, and what's the best next move to get the specific document without a full restore?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself manually verifying snapshot completion and integrity, which is tedious and…+
I often find myself manually verifying snapshot completion and integrity, which is tedious and prone to human error.
I often find myself manually verifying snapshot completion and integrity, which is tedious and prone to human error. This takes up valuable time and adds anxiety. What habit should I change in how I manage our snapshot lifecycle to automate these checks and gain confidence that our backups are consistently reliable and ready for restoration when needed?
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.