◆ Elasticsearch

View completed Elasticsearch tasks

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 taskShow me all completed snapshot tasks from the last 24 hours. I need to confirm that yesterday's…+
Show me all completed snapshot tasks from the last 24 hours. I need to confirm that yesterday's daily backup ran successfully for the 'production-data' repository.
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 the success rate of our daily data synchronization, show me all completed…+
Before I report on the success rate of our daily data synchronization, show me all completed tasks related to the 'data-sync' pipeline over the last week. Group them by status (success/failure) and highlight any recurring failures that might indicate an underlying issue for the data engineering team.
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 critical reindex task for the new product search index shows as completed, but the data isn't…+
A critical reindex task for the new product search index shows as completed, but the data isn't appearing in the application.
A critical reindex task for the new product search index shows as completed, but the data isn't appearing in the application. The product manager is expecting this to be live by now. I'm afraid I've missed something crucial. The task log isn't immediately obvious. What's the most common reason a 'completed' task doesn't reflect actual data availability, and how can I quickly dig into the task's details to find the real issue without causing further delay?
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 just check for 'completed' status without reviewing the full task details, missing…+
I often just check for 'completed' status without reviewing the full task details, missing subtle failures.
I often just check for 'completed' status without reviewing the full task details, missing subtle failures that only surface later. This has led to delayed incident detection and rework. What's a better habit to adopt when reviewing completed tasks to ensure I thoroughly understand their outcome and catch any partial successes or warnings that might become problems?
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.