◆ JavaScript

Monitor and alert system status

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 taskSet up a new alert in Prometheus that fires if the 'api_response_time_p99' metric for the…+
Set up a new alert in Prometheus that fires if the 'api_response_time_p99' metric for the 'checkout_service' exceeds 500ms for more than 5 minutes. Route the alert to the 'on_call_devs' Slack channel.
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 push this new API response time alert for the checkout service, make sure it has clear…+
Before I push this new API response time alert for the checkout service, make sure it has clear runbook links for the on-call team. Also, add a 'warning' threshold at 300ms so we get an early heads-up, and ensure it silences during scheduled maintenance windows.
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 system is sending a flood of 'low disk space' alerts for a non-critical server, but the…+
The system is sending a flood of 'low disk space' alerts for a non-critical server, but the actual disk usage is fine.
The system is sending a flood of 'low disk space' alerts for a non-critical server, but the actual disk usage is fine. The on-call team is getting overwhelmed and starting to ignore alerts, which is dangerous. I suspect a misconfigured threshold or a phantom mount point. I'm afraid of missing a real incident because of the noise. What's the best immediate action to stop the false positives and restore alert credibility?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur monitoring system frequently sends alerts that are either false positives or not…+
Our monitoring system frequently sends alerts that are either false positives or not actionable, leading to alert fatigue.
Our monitoring system frequently sends alerts that are either false positives or not actionable, leading to alert fatigue. This erodes trust and makes it harder to respond to real issues. What habit should I change when setting up new alerts or reviewing existing ones to ensure they are always meaningful and actionable for the on-call team?
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 JavaScript'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.