◆ Elasticsearch

Build integration packages for Elastic Stack

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 taskBuild an integration package for our new payment processing service, so we can ingest its…+
Build an integration package for our new payment processing service, so we can ingest its transaction logs into the Elastic Stack, and make sure it includes pre-built dashboards for monitoring key metrics.
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 finalize this integration package for the marketing analytics service, make sure it…+
Before I finalize this integration package for the marketing analytics service, make sure it has robust field mapping for all custom events, includes a sample dataset for testing, and clearly documents how to extend it for future data sources.
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 new integration package for the inventory system is failing to ingest some critical fields,…+
The new integration package for the inventory system is failing to ingest some critical fields, and the data is showing up as unparsed text.
The new integration package for the inventory system is failing to ingest some critical fields, and the data is showing up as unparsed text. The product team needs this data by end of day for their report, but I can't figure out why the ingest pipeline isn't correctly parsing these specific fields. I've checked the grok patterns, but I'm unsure if it's a data type mismatch or an issue with the source data itself. What's the most likely diagnosis, and what's the quickest way to get this data flowing correctly?
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 find myself rebuilding parts of integration packages because they don't handle schema…+
I often find myself rebuilding parts of integration packages because they don't handle schema changes well or break with new data formats.
I often find myself rebuilding parts of integration packages because they don't handle schema changes well or break with new data formats from source systems. This leads to unexpected downtime for data availability and frustration from data consumers. What habit should I change in how I design and build these packages to make them more resilient to evolving data structures and reduce rework?
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.