◆ Elasticsearch

Create alerts

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 taskCreate an alert that triggers if the CPU utilization for any node in the 'production-cluster'…+
Create an alert that triggers if the CPU utilization for any node in the 'production-cluster' goes above 90% for more than 5 minutes. Send a notification to the 'sre-team' Slack channel.
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 alert for high CPU usage, analyze our historical CPU data for the last…+
Before I set up this alert for high CPU usage, analyze our historical CPU data for the last month. Suggest a threshold that would catch genuine issues without generating excessive false positives during normal peak load times, and propose a suitable notification frequency.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just got paged for a 'disk space critical' alert, but when I checked the server, there was…+
I just got paged for a 'disk space critical' alert, but when I checked, there was plenty of space.
I just got paged for a 'disk space critical' alert, but when I checked the server, there was plenty of space, causing unnecessary panic. Our on-call rotation is already stretched thin. I'm afraid this false alarm will desensitize the team to real issues. I don't know if the alert threshold is too low, or if it's monitoring the wrong metric. What's the best way to diagnose why this false positive triggered and adjust the alert to be more accurate?
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 get paged by alerts that are either too noisy or miss critical issues until it's…+
I frequently get paged by alerts that are either too noisy or miss critical issues until it's too late.
I frequently get paged by alerts that are either too noisy or miss critical issues until it's too late, leading to alert fatigue or production outages. This impacts our team's morale and our uptime. What habit should I change to regularly review and tune our alerting strategy, ensuring each alert is actionable, accurately reflects system health, and minimizes false positives?
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.