Prompt

Code Review & DebuggingPromptIn a pack

Prometheus Metrics Design — Naming, Labels, Cardinality Control, Histograms and Recording Rules

Designs Prometheus metrics that stay useful and affordable — counters, gauges and histograms used correctly, naming and units, label design that avoids cardinality explosions, classic versus native histograms, recording rules for expensive queries, and checks that catch bad metrics before they ship.

  • Role-Based
  • Step-by-Step
  • Constraints
  • Structured Output

Opening lines · ~379 words in full

ROLE: You are a monitoring engineer who has cleaned up Prometheus servers brought down by a single label holding user IDs. Good metrics are cheap and answer real questions, while careless labels multiply series into millions, so you design metric names, types and labels deliberately.

CONTEXT: Services and the questions engineers need answered (latency, errors, saturation, …

Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved

How to use it

  1. Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer.
  2. Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
  3. Want a sharper answer? Ask the AI to check its own draft against your brief before it replies — that is self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique
Step-by-Step

Forces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.

Learn this technique
Constraints

Sets the rules and boundaries — tone, length, what to avoid — that keep the output on-target.

Learn this technique
Structured Output

Pins the response to a defined structure so it drops straight into your workflow.

Learn this technique

Works with

Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.

New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.

More in Code Review & Debugging

Pull Request Review With Severity TriageReviews a pull request diff and returns issues bucketed by blocking, major, minor, and nit severity with concrete fixes.Root-Cause Analysis From a Stack TraceWalks a stack trace and surrounding code step by step to isolate the true root cause and propose a minimal verified fix.Security-Focused Code AuditAudits a code module against the OWASP Top 10 and common weakness patterns, reporting exploitability and remediation.Concurrency And Race Condition HunterInspects multithreaded or async code for races, deadlocks, and visibility bugs and proposes safe synchronization.