◆ Elasticsearch

Retrieve unique count of a field

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 taskGet me the unique count of IP addresses from the `web_logs` index for the last 24 hours,…+
Get me the unique count of IP addresses from the `web_logs` index for the last 24 hours, specifically for GET requests to `/api/v1/users`.
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 acceptI need to quickly see if the number of unique user IPs hitting the `/api/v1/users` endpoint is…+
I need to quickly see if the number of unique user IPs hitting the `/api/v1/users` endpoint is spiking. Before I pull the unique count for the last 24 hours, make sure the query handles potential proxy IP headers and filters out internal network traffic, so the number I get reflects actual external users.
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 unique user count for the `/api/v1/users` endpoint just jumped by 300% in an hour, but our…+
The unique user count for our API just jumped by 300% in an hour, but error rates are flat.
The unique user count for the `/api/v1/users` endpoint just jumped by 300% in an hour, but our error rates are completely flat. I'm afraid this is either a massive, unannounced marketing campaign or a botnet trying to enumerate users. I can't tell if it's legitimate or malicious. What's the most likely diagnosis, and what's the first thing I should check to differentiate between a real traffic surge and an attack?
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 getting surprised by sudden spikes in unique user counts that turn out to be harmless,…+
I keep getting surprised by sudden spikes in unique user counts that turn out to be harmless.
I keep getting surprised by sudden spikes in unique user counts that turn out to be harmless, like new internal tools or a marketing push, and I waste time investigating. What habit should I change to proactively identify and filter out known internal or expected traffic changes from my unique count monitoring, so I only focus on actual anomalies?
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.