◆ Elasticsearch

Set up alerts with ElastAlert

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 taskSet up an alert in ElastAlert for when the average latency across all services in the…+
Set up an alert in ElastAlert for when the average latency across all services in the 'production' environment exceeds 500ms for more than 5 minutes, sending a Slack notification to the #sre-alerts channel. Make sure it only triggers once every 30 minutes.
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 push this new alert for critical service errors, help me make sure it's not going to…+
Before I push this new alert for critical service errors, help me make sure it's not going to flood us with noise. How can I refine the query to only catch truly impactful issues, maybe by correlating with a sudden drop in user traffic or a specific error code that indicates a system-wide failure, rather than just isolated incidents?
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 critical service alert just fired, but the dashboard shows everything is green and users…+
The new critical service alert just fired, but the dashboard shows everything is green.
The critical service alert just fired, but the dashboard shows everything is green and users aren't reporting issues. I'm afraid we're either missing a real problem or the alert is misconfigured and will erode trust. Is this a false positive, or is the dashboard not showing the full picture? What's the fastest way to diagnose the discrepancy and figure out which one it is?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting paged for alerts that turn out to be non-critical or already resolved by our…+
I keep getting paged for alerts that turn out to be non-critical or already resolved.
I keep getting paged for alerts that turn out to be non-critical or already resolved by our auto-remediation. I'm losing sleep and focus. What habit can I change in how I define alert conditions or integrate with our incident response tools so that I only get notified when my intervention is truly required, and not just for informational 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.