◆ Elasticsearch

Monitor Elasticsearch performance

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 taskShow me the current CPU utilization and JVM memory usage for all nodes in the 'production'…+
Show me the current CPU utilization and JVM memory usage for all nodes in the 'production' cluster over the last 30 minutes, and highlight any nodes exceeding 80% CPU or 75% JVM heap.
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 cluster's health, give me a summary of potential performance…+
Before I report on the cluster's health, give me a summary of potential performance bottlenecks. Show me any nodes with sustained high disk I/O, long garbage collection pauses, or queues building up for indexing or search requests over the last hour.
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 'reporting' cluster health just went yellow, but when I check individual nodes, they all…+
The cluster health is yellow, but all nodes appear green individually.
The 'reporting' cluster health just went yellow, but when I check individual nodes, they all appear green and healthy. The data team is waiting for their daily reports, and I'm worried it's a data consistency issue or a shard allocation problem I can't immediately pinpoint. What's the most common reason for a yellow cluster when nodes are green, and what's the fastest way to diagnose which shards are unassigned or problematic?
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 react to performance issues after they've already impacted users, instead of…+
I often react to performance issues instead of proactively identifying them.
I often react to performance issues after they've already impacted users, instead of proactively identifying them. This leads to firefighting and stress. What habit should I change in how I monitor our search engine to anticipate problems like high memory pressure or slow queries before they become critical, so I can intervene earlier and maintain stability?
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.