◆ Elasticsearch

Monitor Elastic Stack with built-in tools

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 taskGenerate a report showing the CPU utilization and memory usage for all nodes in the…+
Generate a report showing the CPU utilization and memory usage for all nodes in the `logging-cluster` over the last 24 hours. Include the average, maximum, and minimum values for both metrics.
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 the Monday morning review, create a dashboard for the `search-cluster` showing its…+
Before the Monday morning review, create a dashboard for the `search-cluster` showing its health. Make sure it highlights any nodes with high GC activity, elevated query latencies, or indexing backlogs from the last week, so we can quickly spot potential issues for discussion.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur main search application is experiencing slow queries, but the general cluster health…+
Our main search application is experiencing slow queries, but the general cluster health metrics look fine, and I can't see an obvious bottleneck.
Our main search application is experiencing slow queries, but the general cluster health metrics look fine, and I can't see an obvious bottleneck. I'm afraid it's a subtle performance issue that's hard to trace, and the users are getting frustrated. I don't know if it's specific query patterns, a particular shard, or something else entirely. What's the most likely diagnosis for localized query slowness when the overall cluster appears healthy, and what's the best next move to pinpoint the root cause?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently struggle to correlate performance issues across different components of the stack,…+
I frequently struggle to correlate performance issues across different components of the stack, leading to longer troubleshooting times.
I frequently struggle to correlate performance issues across different components of the stack, leading to longer troubleshooting times. It feels like I'm always jumping between different views. What habit should I change in how I approach monitoring and visualizing our stack's health to build a more cohesive understanding and quickly connect the dots between related metrics and events?
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.