◆ Elasticsearch

Export data from Kibana to CSV/Excel

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 taskGet the last 30 days of production logs for the 'user-auth' service, filtered by 'ERROR' level,…+
Get the last 30 days of production logs for the 'user-auth' service, filtered by 'ERROR' level, and put them into a CSV file. I need it by 3 PM for the incident review with Sarah.
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 send these 'payment-gateway' service logs to compliance, make sure the CSV is easy for…+
Before I send these 'payment-gateway' service logs to compliance, make sure the CSV is easy for them to work with. Include only the 'timestamp', 'transactionId', and 'errorMessage' fields, and ensure the timestamp is in a standard format they can sort easily.
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 finance team needs a full export of all transactions from the last quarter for their audit,…+
The finance team needs an export of all transactions from the last quarter, but every time I try, the export process crashes after a few minutes.
The finance team needs a full export of all transactions from the last quarter for their audit, but the export keeps failing after a few minutes. I'm afraid of missing the audit deadline. I can't tell them it's a technical limitation. What's the most likely cause of these large exports failing, and what's the best way to get them the data without crashing the system?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm always getting requests for log exports for different teams, and I waste a lot of time…+
I spend too much time manually reformatting log exports for different teams, often missing specific fields they ask for.
I'm always getting requests for log exports for different teams, and I waste a lot of time manually reformatting the CSVs and often miss specific fields they need. This means I'm constantly doing rework and delaying their analysis. What habit should I change to make these exports more consistent and less time-consuming, ensuring I capture all necessary fields upfront?
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.