◆ Elasticsearch

Display logs as a table in Kibana

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 taskShow me the logs from the production cluster for the last hour, formatted as a table, so I can…+
Show me the logs from the production cluster for the last hour, formatted as a table, so I can quickly scan for errors.
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 share these logs with the on-call team, make it easier to see the critical events.…+
Before I share these logs with the on-call team, make it easier to see the critical events. Highlight any entries with 'ERROR' or 'FATAL' severity, and group by service name so they can quickly identify the source.
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 staging environment is suddenly full of 'WARN' messages, but the app is still responding…+
The staging environment logs are showing a flood of 'WARN' messages, but the application seems fine.
The staging environment is suddenly full of 'WARN' messages, but the app is still responding normally. I'm afraid to ignore them, but I also can't tell if it's a real problem or just noisy logging. Could this be a misconfiguration, or is something deeper happening? What's the fastest way to diagnose the actual impact and decide if I need to escalate before the morning stand-up?
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 manually sifting through logs for transient issues that often resolve…+
I keep getting pulled into log analysis for transient issues that resolve themselves.
I spend too much time manually sifting through logs for transient issues that often resolve themselves before I can even pinpoint the cause. This is burning my time and making me less proactive. What habit should I change to more effectively triage these intermittent problems without getting bogged down in every alert, so I can focus on systemic improvements?
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.