◆ Apache Cassandra

Generate Cassandra reports and analysis

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 taskGenerate a report on the read and write latencies for the 'customer_transactions' keyspace over…+
Generate a report on the read and write latencies for the 'customer_transactions' keyspace over the last 24 hours, broken down by individual nodes in datacenter1. Export it as a CSV.
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 acceptI need to understand the performance trends for our 'user_profiles' keyspace. Generate a…+
I need to understand the performance trends for our 'user_profiles' keyspace. Generate a comprehensive analysis of its read and write performance, including p99 latencies and throughput, over the last week. Highlight any significant deviations or anomalies that might indicate a problem, and suggest areas for optimization.
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 analytics team just reported that their complex queries against the 'events_log' keyspace…+
Our analytics team is complaining about slow query times, and I'm not sure where the bottleneck is.
The analytics team just reported that their complex queries against the 'events_log' keyspace are taking significantly longer than usual, impacting their end-of-quarter reporting. I've checked basic metrics, but nothing immediately stands out. I'm worried about missing the Friday deadline for their report. What's the most likely diagnosis for the slowdown, and what's my best next move to pinpoint the exact bottleneck?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI find myself spending too much time manually sifting through various metrics and logs whenever…+
I struggle to quickly identify the root cause of performance issues when they arise.
I find myself spending too much time manually sifting through various metrics and logs whenever a performance issue pops up. It's a reactive approach that delays resolution. What habit should I change to more quickly and accurately diagnose performance bottlenecks across our Cassandra clusters, so I can provide faster answers to the product manager?
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.