Error log analyzer

What this analyzer does

An error log is mostly repetition: the same fault, thousands of times, with a different path or request id each time. This tool normalises each message into a signature — numbers, quoted strings, hex ids and paths are replaced with placeholders — so a thousand lines collapse into the handful of distinct problems actually worth fixing, ranked by how much of the log each one accounts for.

Every signature is then classified by root cause: a missing file, an upstream timeout, a permission problem, resource exhaustion, an application fatal, a TLS handshake failure or a configuration fault. Each class carries a different fix, and the Predictions tab states which one applies.

What an error log cannot tell you

Error logs record what the server chose to write down. A fault that was caught and handled silently never appears, and log levels are set by configuration, so an empty log can mean a healthy service or a quiet one. Timestamps also lack request correlation unless your format adds it, so pairing this with the access log for the same window is usually what identifies the cause.

Privacy

Logs routinely contain personal data, internal hostnames, usernames and sometimes credentials. Files and pasted text are processed entirely in your browser and are never sent to QCRAMAI. Review and redact before sharing any exported output. Each analysis is limited to 200,000 non-empty lines and files to 25 MB.