◆ Elasticsearch

Return specific fields from Elasticsearch

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 taskFrom the 'user-activity-2023.10.26' index, get me just the 'user_id' and 'action_type' fields…+
From the 'user-activity-2023.10.26' index, get me just the 'user_id' and 'action_type' fields for all documents. I need to quickly audit recent user actions.
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 hand this data over to the compliance officer, pull the 'transaction_id', 'amount',…+
Before I hand this data over to the compliance officer, pull the 'transaction_id', 'amount', and 'timestamp' from the 'payments-2023.11.01' index, but make sure the timestamps are in UTC and not local time. They're very particular about timezones.
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'm trying to retrieve the 'error_message' field from the 'app-logs-prod' index for a specific…+
I'm trying to retrieve 'error_message' from the 'app-logs-prod' index, but it's returning empty for critical errors where I know the message exists.
I'm trying to retrieve the 'error_message' field from the 'app-logs-prod' index for a specific incident, but it's returning empty or 'null' for documents where I'm certain the message should be present. I'm afraid I'm missing critical debugging information. What's the most likely reason a field would appear empty when the data is known to exist, and how do I confirm the actual field name or mapping?
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 pulling entire documents when I only need a few fields, which makes my queries slow and…+
I often pull too much data, slowing down my queries and overwhelming my local tools.
I keep pulling entire documents when I only need a few fields, which makes my queries slow and clogs up my local environment. This wastes time and resources. What habit can I build to consistently narrow down my field selection to only what's necessary, especially when troubleshooting or generating reports?
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.