Alternatives
Products that do what Observer does
Live logs inside your IDE to Debug without context switching
- 1TT
2021 · replay.io
- 2
- 3AW
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer…
2024
- 4
- 5
- 6
- 7
- 8
- 9VT
Hi All, this is Shardul here - I am the co-founder of Videobug. https://bug.video We are super excited to share Videobug with you. Videobug records run time code execution so that developers can watch it line by line as frequently as they want, right in their IDE. It takes away the pain of recreating exact conditions that led to a bug and saves developer time in every bug squash. Parth (my co-founder) and I have worked on multiple production grade applications in startups and enterprises. We used Logrocket, Sentry, and Datadog for logging and found ourselves adding more logs after…
2022
- 10LL
Hey HN, I just built an experimental VSCode extension called LLM Debugger. It’s a proof-of-concept that lets a large language model take charge of debugging. Instead of only looking at the static code, the LLM also gets to see the live runtime state—actual variable values, function calls, branch decisions, and more. The idea is to give it enough context to help diagnose issues faster and even generate synthetic data from running programs. Here’s what it does: * Active Debugging: It integrates with Node.js debug sessions to gather runtime info (like variable states and stack traces). *…
2025 · github.com
- 11UO
Hello HN! Parth, and Shardul here. We have been building unlogged.io for the last 21 months. We started as a time travel debugger and pivoted to record and replay with assertions, mocking, and code coverage. You can save the replays in the form of a JSON and commit them to your git. Both Parth and I come from an e-commerce/payments background where production bugs meant heavy financial losses. Big billion days/Black Friday sales meant months of code freezes with low productivity. Before committing the code, we wanted to replay production traffic and know the breaking changes right…
2023
- 12TT
Hi HN, I'm the CEO at https://replay.io. We've been building a time travel debugger for web apps for several years now (previous HN post: https://news.ycombinator.com/item?id=28539247) and are combining our tech with AI to automate the debugging process. AIs are really good at writing code but really bad at debugging -- it's amazing to use Claude to prompt an app into existence, and pretty frustrating when that app doesn't work right and Claude is all thumbs fixing the problem. The basic reason for this is a lack of context. People can use devtools to understand…
2025 · nut.new
- 13WB
Hey hn! I'm one of the co-founders of highlight.io, an open source monitoring tool. Today we're sharing a ClickHouse-based logging solution we've been working on. We wanted to showcase how we built it and share how you could try it out to give feedback. Since we started working on highlight.io, we've been hyper-focused on "cohesion", or ensuring that when you install your monitoring stack, all of the resources in that stack (user interactions, requests, traces, logs, etc.) are connected in a consumable way. We've written up more about our philosophy on this here [1]. We started building…
2023 · github.com
- 14SY
Hey HN, we’re Nico and Arseniy, co-founders of Superlog (https://superlog.sh). We're building a self-installing, self healing observability tool meant not to be opened. It has a wizard that daily sets up proper logging and an agent that investigates errors and opens PRs. Super short demo: https://www.youtube.com/watch?v=xFhU9Mk247M. In our earlier startups, we tried Sentry, Datadog, Grafana, Dash0, and nothing was good enough. Proper telemetry and alerting still requires a ton of manual setup. We struggled with adding good logs, so debugging was tough, especially as…
May 2026 · superlog.sh
- 15
- 16FA
Hey HN, the is Chris, creator of FireDBG. We’ve been working on this debugger just about a year now. Time travel debugging isn’t a new concept, the new idea here is to use call tree visualisation to help us navigate the debug trace. It supports various Linux distros on x64 and macOS on x64 and M1. It’s only available for Rust right now, but we do want to bring this debugging experience to other programming languages. Please give it a try! Would love to know your thoughts. What’s your anecdote in debugging programs? My stupidity is usually in the form of: after a few hours of debugging, I…
2023 · firedbg.sea-ql.org
- 17DC
I've been programming since I'm 6 and I don't want to quit. Since Agents came into existence I've been increasingly building more of the random ideas. BUT, like many I kept getting stuck and frustrated where I wanted to make changes with the Agent that I knew I could've made without it but I had *no clue* how things worked. I created Intraview to help me build and maintain a mental model of what I was building (or had vibed) so I could use my knowledge to either fix it myself, or provide more directed instruction. It grew into something that's transformed my workflow in a pleasant way.…
Nov 2025 · intraview.ai
- 18MC
Hi HN, I'm Kaushik, and I built Rocketgraph. I believe that while other spaces have caught up to the AI wave, the observability space is still lagging behind, using the same tools and dashboards that we use to analyse logs from human-written code. But now the code is written and debugged by AI, so we need to rethink how we do observability where the observer itself is an AI. The problem that I run into is when an alert fires, I have to manually check the Grafana dashboards and write LogQL queries, which is pretty much like greping. But production usually breaks due to a schema mismatch, or a…
Jun 2026 · github.com
- 19MA
2023 · exploit.observer
- 20LZ
Hey HN We’ve been building Logdash as a lightweight observability tool for side projects and prototypes. Most logging/metrics tools (Prometheus, Grafana, ELK...) are amazing, but feel like overkill when you're just hacking on something small. Logdash gives you: - Real-time logs and custom metrics - Zero config (no YAML, no setup) - One tiny SDK to drop in - Hosted UI with live dashboards We use Logdash to monitor Logdash — our own prod dashboard is public here: https://logdash.io/demo-dashboard Would love feedback, ideas, or questions!
2025 · logdash.io
- 21AV
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…
2025 · github.com
- 22
- 23PI
Ladies and gentlemen of a Lisp persuasion, Clojurians and Clojuristas, followers of the paren and everyone else covetously eyeing the greener grass, I made an open-source thing that I would like to share with you. My elevator pitch is that it'll make you forget all about regular print debugging in 10 minutes straight. The slightly longer pitch is this: #>(tag'n'trace any Clojure(-Script) form to `tap>` and Portal with automatic last-input function replay on eval, instant re-render and hassle-free insertion of traced data into the REPL) And before I end up pasting half the README here in bits…
2023 · github.com
- 24RT
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →