◆ Elasticsearch

Return unique values 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 taskI need a list of all unique 'user_id' values from the 'access-logs-2023-11' index. The security…+
I need a list of all unique 'user_id' values from the 'access-logs-2023-11' index. The security team needs this by end of day for their audit report.
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 give the security team this list of unique 'ip_address' values from the…+
Before I give the security team this list of unique 'ip_address' values from the 'firewall-events' index, can you help me refine it? I need to make sure it's actionable. Exclude any private IP ranges, count the occurrences for each unique IP, and sort them by frequency, showing the top 100, so they can prioritize their investigation.
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 product manager just asked for a list of all unique 'feature_flag' values currently active…+
The product manager just asked for a list of all unique 'feature_flag' values currently active in production, but I know some old flags are still present in the data.
The product manager just asked for a list of all unique 'feature_flag' values currently active in production, but I know some old flags are still present in the data even if they're not actively used. I'm afraid of providing misleading information about our current feature set. She needs this for her Q4 planning meeting tomorrow. How can I get a list of unique feature flags that are truly active, filtering out any that haven't been seen in the last 30 days?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often need to extract unique values from various fields across different indices for…+
I often need to extract unique values from various fields across different indices for reporting.
I often need to extract unique values from various fields across different indices for reporting, and I find myself constantly re-writing similar aggregation queries. This repetitive work is consuming too much of my time. What habit should I change to more efficiently generate these unique value lists, especially when the fields and indices are similar in structure but vary by project?
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.