◆ Apache Cassandra

Build a Grafana dashboard

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 taskBuild a Grafana dashboard showing the CPU utilization and memory usage for all production…+
Build a Grafana dashboard showing the CPU utilization and memory usage for all production database servers, refreshing every 30 seconds.
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 hand this Grafana dashboard over to the ops team, can you add alerts for when CPU…+
Before I hand this Grafana dashboard over to the ops team, can you add alerts for when CPU utilization exceeds 80% or memory usage hits 90% for more than 5 minutes? They need to be notified proactively, not just see a red line. I want this dashboard to be actionable for them.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm building out the new database performance dashboard, and I need to include disk I/O…+
I'm trying to build a new Grafana dashboard for our database performance, but I can't find the right metrics for disk I/O latency.
I'm building out the new database performance dashboard, and I need to include disk I/O latency, but I can't seem to locate that specific metric in our monitoring system, or it's named something obscure. If I launch the dashboard without it, the ops team won't have the full picture, and it won't be as useful as it needs to be. Where should I look for this metric, or is there an alternative way to represent disk performance that's readily available?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often get requests for new dashboards, but I spend an excessive amount of time trying to…+
I frequently spend too much time hunting for specific metrics or figuring out how to visualize complex data for new dashboards.
I often get requests for new dashboards, but I spend an excessive amount of time trying to locate the right metrics across our various monitoring tools or figuring out the best way to visualize complex data streams. This delays delivery and frustrates the teams waiting for insights. What habit can I change to more efficiently discover and integrate metrics for new dashboards, perhaps by maintaining a catalog of common data sources or by standardizing our metric naming conventions?
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.