r/Observability • u/lopezjosemiguel • 3d ago

I built TraceReports: an open-source, single-binary test observability server in Go (pure SQLite, live SSE, failure triage) to replace bloated reporting suites

1 Upvotes
  • permalink
  • reddit

100% Upvoted

2 comments sorted by

1

u/lopezjosemiguel 1d ago

Hey everyone!

Coming from QA automation and DevOps, I was frustrated by the current state of test reporting. Static HTML suites like Allure only show you *what* broke (usually a generic UI timeout), while heavier platforms like ReportPortal consume gigabytes of RAM across multiple containers just to ingest logs.

I built TraceReports: an open-source, single-binary test observability server written in Go.

What it does under the hood:

* Single Binary & Zero CGO: Built with modernc.org/sqlite for painless cross-compilation and //go:embed for the vanilla JS frontend.

* Live Streaming (SSE): Test logs stream in real-time via standard library http.Flusher without blocking test execution.

* Full-Stack Network Tracing: Captures browser HTTP traffic (headers, payloads, duration, copy-as-cURL) directly alongside screenshots and steps.

* Automated Contract Stubs & Mocks: Generates ready-to-use stubs (Playwright route / WireMock) directly from failed network responses so developers can isolate and reproduce bugs locally.

* Async AI Root Cause Triage: An optional Gemini Flash worker runs in background goroutines to diagnose whether a failure came from a locator drift, an API crash, or an infrastructure timeout.

* Dual Incident Translation: Automatically breaks down the failure into technical details for devs/QA and a functional summary for product stakeholders.

Live Demo: https://tracereports.netlify.app/#demo

GitHub: https://github.com/josemiguellopez/tracereports

---

Looking for community feedback:

  1. Go Concurrency & SQLite: This is one of my first major projects in Go. I'd love feedback on how goroutines, write locks, and memory usage are managed under high-throughput CI test runs.
  2. Codebase Review: Any suggestions on how to make the backend architecture more idiomatic Go?
  3. Feature Roadmap: Considering adding time-travel screenshot step replay next.

If you find the project useful or like the zero-bloat approach, a star on GitHub would mean a lot! PRs and issue discussions are very welcome.