◆ Elasticsearch

Manage alarms

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 taskAcknowledge the `database-replication-lag` alarm that fired an hour ago and is still active.…+
Acknowledge the `database-replication-lag` alarm that fired an hour ago and is still active. Confirm that the replication status is now healthy and then resolve the alarm, adding a note about the successful failover completion.
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 resolve this batch of `disk-space-low` alarms for the staging environment, analyze the…+
Before I resolve this batch of `disk-space-low` alarms for the staging environment, analyze the trend over the last month. Are these recurring on the same nodes, or is it a new pattern? Suggest if we need to adjust the threshold for staging or if there's a deeper storage management issue we should address.
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 critical `JVM-heap-usage` alarm on the `reporting-service`, but when I…+
I just got paged for a critical `JVM-heap-usage` alarm on the `reporting-service`, but when I checked the host, CPU and memory look normal, and the service seems responsive.
I just got paged for a critical `JVM-heap-usage` alarm on the `reporting-service`, but when I checked the host, CPU and memory look normal, and the service seems responsive. I'm afraid of dismissing a real problem, but I also don't want to waste time chasing ghosts. Is this a transient spike, a misconfigured alert, or something else I'm missing? What's the best next step to quickly determine the alarm's validity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time triaging alarms that turn out to be false positives or low-priority…+
I spend too much time triaging alarms that turn out to be false positives or low-priority issues, distracting me from critical work.
I spend too much time triaging alarms that turn out to be false positives or low-priority issues, distracting me from critical work. This constant context-switching kills my focus. What habit should I change to more effectively manage and refine our alarm definitions, so I'm only responding to truly actionable alerts that demand my immediate attention?
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.