◆ Elasticsearch

Fetch data 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
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 taskFetch the last 100 log entries from the 'nginx_access_logs' index where the 'response_code' is…+
Fetch the last 100 log entries from the 'nginx_access_logs' index where the 'response_code' is 404 and the 'client_ip' is '192.168.1.10'. Display the 'timestamp' and 'request_path' fields.
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 off this data to the security team, let's make it more actionable. Can you not…+
Before I hand off this data to the security team, let's make it more actionable. Can you not just fetch 404 errors for that IP, but also aggregate them by 'request_path' and count how many times each path was hit, ordered by frequency, for the last 24 hours? This will help them see patterns.
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 fetch all activity for user 'john.doe' from the 'user_events' index over the last…+
I'm trying to fetch specific user activity data, but the query is taking too long and timing out.
I'm trying to fetch all activity for user 'john.doe' from the 'user_events' index over the last week, but the query keeps timing out after 30 seconds. The product manager needs this data for an urgent report, and I'm afraid of crashing the cluster with a brute-force approach. I can't tell if the index is too large, the query is inefficient, or if there's an underlying cluster issue. What's the most likely reason for the timeout, and what's the most efficient way to get this user's data without impacting other services?
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 spend too much time crafting and refining queries to pull specific, complex data sets…+
I frequently struggle to retrieve specific, complex data sets from Elasticsearch efficiently for ad-hoc requests.
I often spend too much time crafting and refining queries to pull specific, complex data sets from our data store for various stakeholders, often resulting in slow queries or incomplete results. This constant struggle makes me feel like I'm not fully leveraging our data. What habit should I change to more quickly and accurately fetch the precise data needed for ad-hoc requests, without repeatedly hitting performance bottlenecks or missing crucial details?
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.