Show HN: A VS Code extension to visualise Rust logs in the context of your code

[arthurgousset]

We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone.

This saves you from browsing logs and trying to make sense of them outside the context of your code base.

We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened.

It's a prototype [2], but if you're interested, we’d love some feedback.

---

References:

[1]: VS Code: marketplace.visualstudio.com/items?itemName=hyperdrive-eng.traceback

[2]: Github: github.com/hyperdrive-eng/traceback

[3]: Crate: docs.rs/tracing/latest/tracing

[westurner]

Good idea!

This probably saves resources by eliminating need to re-run code to walk through error messages again.

Integration with time-travel debugging would even more useful; https://news.ycombinator.com/item?id=30779019

From https://news.ycombinator.com/item?id=31688180 :

> [ eBPF; Pixie, Sysdig, Falco, kubectl-capture,, stratoshark, ]

> Jaeger (Uber contributed to CNCF) supports OpenTracing, OpenTelemetry, and exporting stats for Prometheus.

From https://news.ycombinator.com/item?id=39421710 re: distributed tracing:

> W3C Trace Context v1: https://www.w3.org/TR/trace-context-1/#overview

[arthurgousset]

Thanks for sharing all these links, super handy! I really appreciate it.