◆ Elasticsearch

Archive 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 taskArchive all snapshots older than 90 days from the 'log-history' repository to long-term cold…+
Archive all snapshots older than 90 days from the 'log-history' repository to long-term cold storage. Confirm deletion from the active repository afterward.
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 archiving these old snapshots, review the access patterns for the 'security-audits'…+
Before archiving these old snapshots, review the access patterns for the 'security-audits' snapshots. We've had compliance requests for data older than 90 days, so make sure those specific snapshots are moved to an accessible cold storage tier, not just deleted.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new compliance mandate just came down for 'user-activity' logs, requiring a two-year…+
A new compliance requirement just came in for our 'user-activity' logs, demanding retention for two years, but we've been archiving snapshots after 90 days.
A new compliance mandate just came down for 'user-activity' logs, requiring a two-year retention period, but our current policy archives snapshots after 90 days. I'm afraid we've already lost crucial historical data or that retrieving it will be a nightmare. What's the immediate impact of this policy change on our existing archives, and what's the best first step to assess our current compliance posture and prevent future gaps?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe're repeatedly finding that our snapshot retention policies are out of sync with evolving…+
We keep running into situations where our snapshot retention policies don't align with evolving compliance or business needs, leading to data gaps or frantic data recovery.
We're repeatedly finding that our snapshot retention policies are out of sync with evolving compliance mandates or business needs, resulting in either data gaps or frantic, last-minute data recovery efforts. This constant reactive scramble is unsustainable. What habit should I change in how we define or review our snapshot archiving strategy to ensure it proactively meets future demands?
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.