◆ Elasticsearch

Restart Elastic Agent

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 taskRestart the Elastic Agent on the 'log-collector-prod-01' server. I need it to pick up the new…+
Restart the Elastic Agent on the 'log-collector-prod-01' server. I need it to pick up the new log path immediately.
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 restart the agent on 'web-app-07', check if there are any pending updates or policy…+
Before I restart the agent on 'web-app-07', check if there are any pending updates or policy changes for that specific agent. I want to make sure it comes back up with the latest configuration and doesn't just re-read an old one.
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 restarted the agent on 'billing-service-03' because it was showing as unhealthy, but…+
I just restarted the agent on 'billing-service-03' because it was showing as unhealthy, but it's still red in Fleet after five minutes. I'm afraid of an underlying issue that a simple restart won't fix, and the billing team is already asking why their dashboards are empty. Is this a common delay, or should I be looking for something else immediately?
I just restarted the agent on 'billing-service-03' because it was showing as unhealthy, but it's still red in Fleet after five minutes. I'm afraid of an underlying issue that a simple restart won't fix, and the billing team is already asking why their dashboards are empty. Is this a common delay for agents to report back after a restart, or should I be looking for something else immediately, like network issues or a corrupted agent state, to get it reporting again?
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 restart agents only to find they haven't picked up the latest policy, leading to…+
I frequently restart agents only to find they haven't picked up the latest policy, leading to more troubleshooting.
I frequently restart agents only to find they haven't picked up the latest policy, leading to more troubleshooting. What habit should I change to reliably confirm an agent has applied its latest assigned policy *before* or *immediately after* a restart, so I don't waste time debugging outdated configurations?
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.