Parse Python exception logs

Parsing Python exception logs involves breaking down the traceback to understand what error occurred, where it occurred, and what caused it. Here’s how you can systematically parse and understand a typical Python exception log:

📌 Structure of a Python Exception Log

A Python traceback log generally has the following structure:

python
CopyEdit
Traceback (most recent call last):
  File "script.py", line 10, in <module>
    result = divide(10, 0)
  File "script.py", line 5, in divide
    return x / y
ZeroDivisionError: division by zero

🧩 Key Components

1. Traceback (most recent call last):
   Indicates the start of the stack trace. It’s a chronological list of calls the interpreter made that led to the exception.

2. File name and line number:
   Each File entry tells you where the call was made:

   • "script.py", line 10, in <module> — shows the top-level call.

   • "script.py", line 5, in divide — shows the internal function call.

3. Code snippet:
   The line of code that was executed is shown under each file/line entry.

4. Exception Type and Message:
   At the bottom is the actual exception:

   • ZeroDivisionError is the exception type.

   • division by zero is the error message.

🛠 How to Parse Programmatically (Basic Example)

You can parse logs using regex or libraries like traceback and re. Here’s a simple example using Python:

python
CopyEdit
import traceback

try:
    1 / 0
except Exception:
    log = traceback.format_exc()
    print("Full Traceback:n", log)

    lines = log.strip().split('n')
    for line in lines:
        print("Parsed line:", line)

To extract structured info:

python
CopyEdit
import re

def parse_traceback(traceback_str):
    pattern = r'  File "(.*?)", line (d+), in (.*?)ns+(.*)'
    matches = re.findall(pattern, traceback_str)
    exception = traceback_str.strip().split('n')[-1]

    parsed = {
        "calls": [{"file": f, "line": int(l), "function": fn, "code": code}
                  for f, l, fn, code in matches],
        "exception": exception
    }
    return parsed

🧪 Example Output for Above Parser

Given this input traceback:

text
CopyEdit
Traceback (most recent call last):
  File "main.py", line 12, in <module>
    calculate()
  File "main.py", line 8, in calculate
    return 10 / 0
ZeroDivisionError: division by zero

The parser would output:

json
CopyEdit
{
  "calls": [
    {
      "file": "main.py",
      "line": 12,
      "function": "<module>",
      "code": "calculate()"
    },
    {
      "file": "main.py",
      "line": 8,
      "function": "calculate",
      "code": "return 10 / 0"
    }
  ],
  "exception": "ZeroDivisionError: division by zero"
}

🔍 Advanced Options

For more robust log analysis:

• Use the logging module with exc_info=True

• Use third-party libraries:

  • sentry-sdk

  • loguru

  • better-exceptions for dev-time clarity

✅ Tips for Effective Debugging

• Start at the bottom: The actual exception is there.

• Work backward: Follow the stack trace to understand the sequence of calls.

• Check variable values: Consider logging variables near the crashing line.

• Use tools: Integrated tools like PyCharm or VS Code make traceback navigation easier.

If you have a specific traceback you want parsed or analyzed, feel free to paste it here.