Alternatives
Products that do what Observer does
Live logs inside your IDE to Debug without context switching
- 1
- 2
- 3VT
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
- 4
- 5
- 6
- 7
- 8IR
Sharing an internal tool that accelerated my development work 10-fold, especially with API debugging. Thought fellow developers here might find it useful. As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc. After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and…
2018
- 9LZ
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
- 10AV
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
- 11
- 12WV
Hi HN, I'm the CEO at https://replay.io. We've been working on time travel debugging for web development for a while (https://news.ycombinator.com/item?id=28539247) and more recently an AI app builder that uses that debugger to get past problems instead of spinning in circles (https://news.ycombinator.com/item?id=43258585). We've gotten to where we can pretty easily build apps to replace business-critical SaaS tools, some of which we're now using internally: * We built our own issue tracker to keep track of all our development projects, tickets, bug…
Dec 2025
- 13MY
LLM observability is an absolute must-have for anyone running something in prod (or prod-like). While all the observability startups are great, you're essentially sending all your OpenAI usage history - prompts, generations, chats - to a random third party. So this script deploys a basic proxy in your Azure account, catches all incoming OpenAI requests, stores logs in your own resource group, and comes with visualizations premade (charts, timelines, chat history, cost estimation, etc). Thanks for any thoughts and feedback!
2023 · github.com
- 14CT
I built CodeBeam to solve two core developer frustrations: constant context-switching between browser and IDE, and the tedious process of dealing with errors across different languages and frameworks. What makes CodeBeam different is its universal adaptability. It watches your clipboard with customizable directives for automatic file operations, while simultaneously monitoring your logs for errors using pattern-based detection that works with any language or framework. When it spots an error, it automatically generates AI-ready prompts with rich context, making debugging significantly…
2025 · github.com
- 15LLiveCoder▲18
LiveCoder is a fun tool I built almost a year ago to simulate live coding Frontend technologies for my presentations. You actually don't have to live-code, but just prepare beforehand the program, snippets of HTML, CSS and Javascript and you feed the tool with it, so you can just focus on explaining what's being coded. Simple :-) I never really shared this tool, but I used it in a few presentations quite succesfully, so I think it could be an interesting tool to use. You have full control of the speed. You can pause and resume... An entire app can be live-coded with this. It's quite fun to…
2017
- 16IM
Hello I'm Jack, I was previously a Site Reliability Engineer and i've been working on monitro.dev which makes log monitoring simple for individuals or small teams. It allows you to easily forward any logs to multiple channels such as Slack, Discord & Telegram. The events are also viewable though the admin dashboard and are easily filterable. Currently there is only an NPM package with javascript / typescript support but i have plans to expand this to other languages such as Python, Rust etc. The package has many options, one of them is forwarding any uncaught exception and as an event…
2024 · monitro.dev
- 17IB
Logging and tools like Sentry are a thing of the past. A while back on a night out in northern Norway, I had to start debugging a critical production bug that broke the payment flow of my SaaS product. I had limited time to fix the bug or I would have lost about ~1K profit. Super stressful. I had logging and Sentry in place, but neither helped me reproduce or find the root cause of the bug. Ever since, I started thinking; why can’t we just have a tool that you setup once, and that allows us to reproduce every function call and function that the user ran before the bug? This is how the idea…
2023 · useflytrap.com
- 18LA
Hey HN, I'm sure many of you have encountered statically-typed codebases so large and complicated that your code editors freeze, lag, become unresponsive, and generally struggle. Debugging a slow editor is involved and usually an unwelcome distraction. In many cases, slowness in code editors comes from language servers, which are external programs that provide language features (e.g. go-to-definition, diagnostics, type hints). Examples of developer frustrations: [1] and [2]. At a previous company, we were concerned about growing internal frustrations from editors bottle-necked by slow…
2025 · github.com
- 19LA
Hello HN! I'm an Android OS engineer. I've worked with AOSP and Linux kernels all my career and always wondered about lack of sophisticated tools to debug and analyze system-level logs. Always had to resort to manually skimming through large log files to find something I needed to. With the rise of LLMs and the AI-age, I felt it was a great opportunity to build something for OS engineers, which is what led to logcat.ai! We are building the industry-first observability platform for system level intelligence. Think "Datadog for operating systems" instead of applications. Currently, we support…
2025 · logcat.ai
- 20GY
Hi all, I've been working on this devtool for 1 month now for myself at first and I'll be curious to see if it's something that could work for you as well. So basically, it detects bugs in your website in production from real user sessions, an llm clusters them by severity and it provides the complete context of the issue that you can copy-paste into your coding agent to fix it in one go. Why did I create it? I've been shipping fast with tools like Cursor and Claude Code. The problem? When bugs happen in production, these tools have zero context about what actually went wrong. Sentry is…
Nov 2025 · sonarly.dev
- 21IL
VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less. So I built my own IDE around that workflow. Terminals are a first-class citizen, every project stays alive in the background with visual statuses. Close the workspace and come back weeks later, everything is still in its place. I've been using it for weeks and it's a big productivity boost. The…
Jul 2026 · github.com
- 22CL
No more copy-pasting logs when troubleshooting issues—the vibes told me there had to be a better way. Now debugging flows like a conversation.
2025 · github.com
- 23TN
Telescope originally started as a ClickHouse-focused log viewer. But while building it, I kept running into the same pattern: when everything worked, logs were in ClickHouse. When things broke, logs were still inside Kubernetes. That gap led to adding Kubernetes as a native log source. This is not meant to replace proper log aggregation. Centralized storage with indexing and retention policies is still the right approach for production. But there are situations where aggregation doesn't help: the logging pipeline is broken, logs are delayed, or you're debugging locally and don't have a…
Feb 2026 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →