◆ Elasticsearch

Configure Elastic SNMP integration

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 taskConfigure the Elastic SNMP integration to collect network device metrics from the Cisco router…+
Configure the Elastic SNMP integration to collect network device metrics from the Cisco router 'core-router-01' and the Juniper switch 'dist-switch-05', using community string 'public' for initial setup. Send the data to the 'network-ops' data stream by end of day, so the network team can start monitoring.
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 enable this SNMP integration for 'core-router-01' and 'dist-switch-05', help me ensure…+
Before I enable this SNMP integration for 'core-router-01' and 'dist-switch-05', help me ensure we're collecting the most relevant metrics without overwhelming our storage. What are common OIDs or metric sets that are crucial for network performance monitoring and troubleshooting, and which ones are usually safe to exclude to reduce data volume? Flag any settings that could impact the devices' performance or our ingestion costs for the network operations lead.
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 SNMP integration is collecting some data from 'core-router-01', but critical interface…+
The SNMP integration is collecting some data, but critical interface metrics are missing from the router.
The SNMP integration is collecting some data from 'core-router-01', but critical interface metrics like bandwidth utilization are completely missing, even though the device is configured to send them. The network team needs these for their capacity planning report by Friday. I'm unsure if it's a specific OID issue, a data type problem, or a parsing error. What's the most common reason for specific SNMP metrics to be absent, and what's the quickest way to verify the data being received?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy SNMP integrations often miss key metrics or collect irrelevant data, requiring iterative…+
SNMP integrations often miss key metrics, requiring iterative debugging after deployment.
My SNMP integrations often miss key metrics or collect irrelevant data, requiring iterative debugging and adjustments after deployment. This delays the network team's ability to monitor effectively and costs me extra time. What habit should I change to ensure a more precise and complete SNMP metric collection from the initial setup, reducing the need for post-deployment fixes?
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.