◆ Elasticsearch

Automate tasks with Elastic Workflows

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 taskCreate an Elastic Workflow that runs every Sunday at 2 AM to automatically snapshot all indices…+
Create an Elastic Workflow that runs every Sunday at 2 AM to automatically snapshot all indices named 'production_data-*' to the S3 repository 'backup-archive'. Make sure it notifies me via email if the snapshot fails.
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 set up this weekly snapshot workflow for production data, let's refine it. Can we add…+
Before I set up this weekly snapshot workflow for production data, let's refine it. Can we add a step to first check the health of the 'production_data' indices, and only proceed with the snapshot if they are green? If not, send an alert to the SRE team before attempting the snapshot.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe automated weekly snapshot workflow for 'production_data' indices has failed twice in the…+
My automated snapshot workflow keeps failing intermittently, but the logs aren't clear about the root cause.
The automated weekly snapshot workflow for 'production_data' indices has failed twice in the last month, but the error messages are generic and don't point to a specific issue. The VP of Engineering is asking why our backups aren't reliable. I'm worried about data loss and can't tell if it's a network glitch, a repository issue, or something with the indices themselves. What's the most likely diagnostic approach to pinpoint these intermittent failures, and what's the best immediate action to ensure our next backup succeeds?
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 constantly double-checking the status of our automated data workflows, even after they…+
I spend too much time manually verifying the success of our automated Elasticsearch maintenance tasks.
I'm constantly double-checking the status of our automated data workflows, even after they report success, because I've been burned by silent failures before. This manual verification is a huge time sink and I'm losing confidence in our automation. What habit should I change to build more robust and trustworthy workflows that truly free up my time, rather than just shifting my anxiety?
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.