◆ Apache Cassandra

Monitor Cassandra database performance

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 taskCheck the latency and throughput metrics for the Cassandra cluster in production for the last…+
Check the latency and throughput metrics for the Cassandra cluster in production for the last 24 hours and report any anomalies.
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 the daily stand-up, pull the key performance indicators for the primary Cassandra…+
Before the daily stand-up, pull the key performance indicators for the primary Cassandra cluster. Highlight any nodes showing elevated read latencies or dropped mutations, making it easy for me to explain potential bottlenecks to the team.
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 finance application users are complaining about slow report generation, but the overall…+
The finance application is reporting slow responses, but I see nothing critical on the main dashboard.
The finance application users are complaining about slow report generation, but the overall Cassandra cluster health looks green. I'm worried it's a specific query or table causing the problem, but I can't pinpoint it without digging deeper into individual node metrics. What's the most likely culprit here, and how should I start investigating 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'm always reacting to database performance issues rather than proactively addressing them.…+
I keep getting caught off guard by performance issues that escalate quickly.
I'm always reacting to database performance issues rather than proactively addressing them. This leads to late nights and stressed-out teams. What daily habit can I adopt to anticipate and mitigate these problems before they become critical, especially with the upcoming peak season?
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 Apache Cassandra'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.