Paste a stack trace that a log pipeline squeezed into one line. The formatter restores the line breaks, indents the frames and can fold away framework noise so your own code stands out.
Runs entirely in your browser — nothing you enter here is sent to a server.
A stack trace is naturally multi-line: an exception message followed by one line per call frame. Structured logging does not get on with that. To keep one event per line, JSON loggers store the trace as a single string with the line breaks written as \n and the indentation as \t. In a log viewer, a terminal or an alert message you then see one very long line that is almost impossible to read.
The formatter reverses that. It finds the trace — on its own or inside a JSON log line — turns the escape sequences back into real line breaks, indents the frames and separates the exception lines from the frames. With folding on, runs of framework frames are collapsed into a single line so the frames from your own code are easy to find.
The exception type and message say what went wrong. Half the time that is all you need.
In chained exceptions the bottom-most cause is usually the real one; the ones above are wrappers added on the way up.
The topmost frame from your own package is where your code met the problem — the line to open in the editor.
Python tracebacks list the most recent call last, with the error at the bottom. Use "reverse order" if you prefer one convention.
Log the trace in its own field rather than inside the message, so tools can render it properly. Most log platforms — and most languages' JSON loggers — have a multi-line or "stack" mode for this. And when you send an exception to chat, send the first line and a link: nobody reads sixty frames in a notification.
Start with the first line: the exception type and message. Then look for the first frame from your own code — that is where your program was when the error occurred. Frames below it show how execution got there.
Paste the line here; escaped \n, \t and \" sequences are converted automatically, including when the trace sits inside a JSON object.
Java and other JVM languages, JavaScript and Node.js, Python, .NET, Go, Ruby and PHP traces are recognised. Any other text with escaped line breaks is still unescaped and laid out.
Those frames are identical to the bottom frames of the enclosing exception's trace, so Java omits them to avoid repetition. Nothing is missing.
Upzilla checks your sites, servers and APIs around the clock and alerts you the moment something breaks. 10 monitors free, no card required.