BugTrace
View demo

Local-first debugging workspace

BugTrace

Request Replay & Investigation Workspace for Microservices

Replay backend requests, collect Kubernetes logs correlated to that replay, compare runs, and investigate microservice behavior.

BugTrace is a request-centric investigation workspace for microservices.

Download macOS app GitHub View Demo
BugTrace desktop workspace with replay request, findings, response viewer, Kubernetes logs, and unified timeline
Local desktop workspace Replay request -> correlate logs -> compare runs

Demo surface

Replay backend requests with the evidence attached.

BugTrace starts from a replayed request and keeps logs, checks, timeline events, run comparison, and report output in the same workspace.

BugTrace demo placeholder showing replay request, logs, timeline, comparison, and report panes

Main workflow

From one failing request to a reviewable investigation.

  1. 01Request replay
  2. 02Logs correlated to the replay
  3. 03Request timeline
  4. 04Findings-oriented comparison
  5. 05Reviewable report

Features

Built around backend debugging loops.

More than a request runner: BugTrace ties replay input to Kubernetes evidence and produces artifacts you can review with the team.

Request replay from curl

Paste or import a curl command and rerun it against the same service path.

Kubernetes logs for that replay

Collect pod, namespace, and container output around the replay window.

Request-centered timeline

Fold request events, logs, checks, and service responses into one sequence.

Investigation history

Keep every run, note, finding, and report tied to the original request.

Deterministic comparison

Compare failed and passed runs without losing the conditions that mattered.

Human-readable checks

Turn service expectations into readable assertions for fast review.

Investigation reports

Generate compact summaries for teammates, Jira comments, or handoff notes.

Pytest draft generation

Convert an investigation into a practical test draft for regression coverage.

Human-readable checks

Write investigation checks like notes.

Express service expectations in a small readable DSL, then keep the result next to the replay and logs.

assert response.items not_empty

Report output

Leave with an engineering artifact.

Checkout replay regression Run #1 failed: upstream returned 500 Run #2 passed: dependency returned data Finding: validation check changed behavior

Investigation example

Two runs, one concrete difference.

BugTrace helps understand what changed between runs without switching between curl output, Kubernetes logs, and handwritten notes.

Run #1FAILED

upstream returned 500

response items empty

Run #2PASSED

upstream healthy

response items returned

Desktop

Local-first by default.

Download the local-first macOS app for Apple Silicon. BugTrace stays close to your kube context, replay input, logs, and investigation history.

  • Local-first
  • macOS desktop app
  • Apple Silicon
  • Kubernetes-aware
  • No cloud dependency
  • Requests and logs stay on your machine
First launch on macOS

If macOS blocks the app after download, run this once in Terminal:

xattr -rd com.apple.quarantine /Applications/BugTrace.app/
Current kube context staging-us-east
Logs source local kubeconfig
Replay input curl request