◆ Elasticsearch

Create a query for not null/empty fields

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 taskI need a query that returns documents where the 'user_id' field exists and isn't an empty…+
I need a query that returns documents where the 'user_id' field exists and isn't an empty string. This is for the 'web_logs' index, and I need the results by Friday for the audit.
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 off to the analytics team, build a query for the 'web_logs' index that…+
Before I hand this off to the analytics team, build a query for the 'web_logs' index that checks for existing 'user_id' values, but also make sure it's efficient and can handle large volumes without slowing down their dashboards.
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 checked the 'web_logs' index and I'm seeing no 'user_id' values for new signups, even…+
The new user signup flow is showing zero 'user_id' entries in the 'web_logs' index, but the database shows successful signups.
I just checked the 'web_logs' index and I'm seeing no 'user_id' values for new signups, even though the database confirms they're happening. I'm afraid we're losing crucial tracking data, and the product manager is asking for conversion rates. I can't tell if the data isn't being indexed, or if the query is wrong. What's the likely issue here, and what's the fastest way to confirm the data is actually flowing?
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 tired of the constant fire drills when critical log fields go missing. It always feels like…+
I keep getting alerts for missing critical fields in our logs, and it's always a scramble to figure out if it's an indexing issue or a data pipeline problem.
I'm tired of the constant fire drills when critical log fields go missing. It always feels like a race to determine if it's an indexing problem or a data pipeline hiccup. What habit should I change to proactively monitor for these missing fields, so I can catch them before they impact reporting or trigger an incident?
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.