◆ Elasticsearch

Troubleshoot Elasticsearch performance problems

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 taskAnalyze the slow search queries on the 'customer-data' index from the last hour and list the…+
Analyze the slow search queries on the 'customer-data' index from the last hour and list the top 5 slowest.
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 optimize the slow queries on 'customer-data', can you help me understand if the issue…+
Before I optimize the slow queries on 'customer-data', can you help me understand if the issue is with the queries themselves, the index mapping, or the underlying hardware? I've tried optimizing queries before, but the performance gains were minimal, and I suspect a deeper problem.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting extremely slow response times for searches on the main application,…+
Users are reporting extremely slow response times for searches on the main application.
Users are reporting extremely slow response times for searches on the main application, impacting sales calls. I'm seeing high CPU usage on the data nodes, but I'm not sure if it's a specific query, a new data ingestion pipeline, or just an unexpected traffic spike. What's the quickest way to pinpoint the bottleneck and alleviate the immediate pressure?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently get complaints about search performance, and I spend too much time firefighting,…+
We frequently get complaints about search performance, and I spend too much time firefighting.
We frequently get complaints about search performance, and I spend too much time firefighting, leading to reactive fixes instead of lasting solutions. This cycle is unsustainable. What habit should I change to proactively monitor and optimize search performance, preventing these recurring slowdowns?
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.