The prompt
Adapt this outline from the official Grok Bot use cases.
Investigate the metric regression since the named release or event. Review dashboards, traces, and flamegraphs; identify the highest-confidence hotspot; return a short write-up with screenshots and direct links. Separate facts from hypotheses. Do not change alerts or production settings.
Rules: never invent a measurement; if access is blocked, say so. How it's set up
Official Product Performance: https://docs.x.ai/grok-bot/use-cases
- Connect observability tools read-first.
- Use routines for recurring health reports — not unsupervised prod edits.
- Distinct from workforce-checker-for-stuck-bots on this site.
Why it works
Incident bots that flip flags are scary. A citation-heavy investigation pack is what on-call actually wants.
This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.