Muhtalip Dede · Founder of kprompt3 min readkprompt + Prometheus: why is my api slow — without inventing numbers
Day-2 Prometheus with kprompt: bind an existing Prom URL, read-only performance explain (CPU, memory, p95, HPA), optimize idle/rightsizing, and fail clear when metrics are missing. Not a PromQL IDE and not auto-remediation.
Prometheus is still the right store for cluster metrics. kprompt does not replace it, and it does not invent a latency number when the backend is missing. It binds the Prometheus you already scrape and compiles “why is my api slow?” into bounded PromQL — then narrates CPU, memory, p95, replicas, and HPA. Read-only. No silent patch.
Helm day-2 has its own deep dive. OpenTelemetry is the traces sibling. This post is metrics: detect, bind-over-install, the performance explain shape, how optimize uses the same URL, and what we refuse to claim.
Prerequisite: a Prometheus URL, not a second stack
kprompt tools reports whether a Prometheus URL is configured. Brownfield instinct is bind the scraper you already run. kprompt setup can plan kube-prometheus-stack — dry-run by default, approve-gated — but that is the exception, not the adopt path.
Detect, then bind
kprompt tools
# prometheus: configured URL — or MissingHint
kprompt config set tools.prometheus.url http://prometheus.monitoring:9090
# Only if you truly have no Prom and accept an install plan:
# kprompt setup --only prometheus --dry-runwhy is my api slow — read-only explain
Performance explain is a read. It uses bounded instant and range queries for a named workload: CPU, memory, p95 latency when the metric exists, replica count, and HPA headroom. Missing Prom fails clear. Partial metrics degrade — they do not fabricate p95.
Performance explain
$ kprompt "why is my api slow?" -n production
# Needs tools.prometheus.url
# Narrates CPU / memory / p95 / replicas / HPA when the series exist
# Does not apply a scale or patchSame family: why is production slow, show CPU for payment-api pods last hour. The Top 100 hub lists the observability set; this post is the contract behind those rows.
What the queries are allowed to do
| Signal | Role | If missing |
|---|---|---|
| CPU / memory | Usage vs requests for the target | Skip that finding — do not invent % |
| p95 latency | When the histogram/series exists | Omit latency — do not guess ms |
| Replicas | Current desired/ready sketch | Fall back to Kubernetes inventory |
| HPA | Present, maxed, or static-replica note | Structural note only |
Timeouts and bounded windows are part of the adapter. kprompt is not a PromQL scratchpad and not a drop-in for Grafana Explore.
optimize uses the same bind
optimize my cluster is a separate read-only report: inventory always, idle and rightsizing when Prometheus usage vs requests supports it, HPA hints from objects. --approve on the optimize prompt does not patch Deployments. Suggested scale/patch plans are follow-ups with their own approval.
Same URL, different intent
kprompt "why is my api slow?" -n production
kprompt "optimize my cluster" -n production
kprompt "optimize my cluster" -o json # CI / jq — still read-onlyMulti-tool: explain, then a plan
You can chain a read into a mutate: why is api slow then scale api to 4. The scale step still produces one aggregate plan and one approval. Metrics narration is not permission to apply.
One approval for the mutating tail
kprompt "why is api slow then scale api to 4" -n production
# read evidence, then a scale PlanResult — y/N or --approveWhat we are not claiming
- Not a PromQL IDE or recording-rule compiler
- Not a replacement for Grafana dashboards (those are a separate bind)
- Not a second kube-prometheus-stack by default — bind first
- Not cloud invoice / FinOps — labeled cost notes only when Prom exists
- Not auto-remediation: slow ≠ silent HPA edit
- Not a promise that every cluster has RED metrics with the names we prefer
Try it against the Prom you already have
Bind → explain → deny a wipe
kprompt tools
kprompt config set tools.prometheus.url http://prometheus.monitoring:9090
kprompt "why is my api slow?" -n staging
kprompt "optimize my cluster" -n staging
kprompt "delete everything in the cluster"
# expect hard deny — metrics never weaken the safety loopExperimental on purpose. Prefer a non-production namespace while you learn the narration. If tools says Prometheus is missing, point at the URL you already scrape — do not install a second stack so the demo looks green.
Related posts
kprompt + OpenTelemetry: trace payment request — without inventing spans
Day-2 OpenTelemetry with kprompt: bind Jaeger or Tempo, walk a span tree, narrate bottleneck waits, enrich service graphs with call edges when traces exist, and degrade honestly when OTel is missing. Not a Jaeger UI and not auto-remediation.
Read articleTop 100 Kubernetes prompts (natural language ↔ kubectl)
A tagged hub of ~100 real Kubernetes ops prompts—Operations, Debug, GitOps, Observability, Security, and Multi-cluster—each with a kubectl or tooling note, linked to our cheat sheet, error playbook, and edge-case guide.
Read articlekprompt + Argo CD: sync status, drift, and approve-gated reconcile
Day-2 Argo CD with kprompt: detect Application CRDs, show gitops sync status, investigate drift vs Git, approve-gated sync/promote/rollback through the real Application API, and optional --gitops PR mode instead of live reconcile. Flux is the peer engine on the same contract. Not an Argo UI and not silent sync.
Read article