◆ Apache Cassandra

Monitor Apache Cassandra 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
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCheck the read and write latencies for the 'product_catalog' keyspace on node 'data-node-01'…+
Check the read and write latencies for the 'product_catalog' keyspace on node 'data-node-01' over the last 30 minutes and flag any values above 50ms.
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 our peak holiday sales, I need to ensure our 'order_tracking' cluster can handle the…+
Before our peak holiday sales, I need to ensure our 'order_tracking' cluster can handle the increased load. I'm worried about potential bottlenecks in read or write paths, especially around the checkout process. Help me identify the most critical metrics to monitor for early warning signs of performance degradation and suggest thresholds that would indicate a problem before it impacts customers.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur 'user_profiles' service is reporting slow responses, but CPU and memory on the Cassandra…+
Our 'user_profiles' service is reporting slow responses, but CPU and memory on the Cassandra nodes look normal.
Our 'user_profiles' service is reporting slow responses, but CPU and memory on the Cassandra nodes look normal. I'm afraid it's a subtle issue like high garbage collection pauses or read contention on a specific table, and I can't tell the product manager I don't know why it's slow. What's the likely diagnosis, and what's the best next move to pinpoint the root cause quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself reacting to performance alerts rather than proactively identifying…+
I frequently find myself reacting to performance alerts rather than proactively identifying potential issues.
I frequently find myself reacting to performance alerts rather than proactively identifying potential issues before they become critical. This leads to firefighting and unplanned downtime. I need to shift from reactive to proactive monitoring. What habit should I change to better anticipate and address database performance problems before they impact our services?
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.