Log Detective
Stack traces in, root cause out
Paste a wall of logs, a stack trace, or a cryptic error message and get a plain-English root-cause analysis plus a likely fix. Great for showing how OpenClaw handles messy technical input.
PROMPT
Analyze these logs and help me find the root cause. Parse the error chain, reconstruct the timeline of what happened, and identify: (1) the root cause — the first thing that went wrong, (2) the cascade — how it led to the visible symptoms, (3) the fix — what to change in code or config to prevent this. Explain in plain English, not just "NullPointerException at line 42." If the logs are from multiple services, correlate them by timestamp. If you need more information, tell me exactly what additional logs or context would help. Logs: [paste your logs, stack trace, or error output here]
How It Works
Instead of manually reading through thousands of log lines looking for the
needle, your Claw parses structured and unstructured logs, correlates
timestamps, identifies the failure chain, and explains what went wrong
in plain English.
What You Get
- Root cause identification from stack traces and error logs
- Timeline reconstruction: what happened in what order
- Correlation across multiple log sources (API, database, worker, etc.)
- Plain-English explanation of the error chain
- Suggested fix with code examples
- Suggestions for what extra logs or context would help if the root cause is still unclear
Setup Steps
- Paste your logs, stack trace, or error output
- Optionally provide context (what action triggered the error)
- Get a diagnosis and fix
Tips
- The more context you give, the better the diagnosis
- Include logs from multiple services if you suspect a cross-service issue
- Ask for a permanent fix, not just a workaround
- Works with any log format: JSON, plaintext, syslog
- Pair with your monitoring stack to analyze alert payloads directly