Why I Built Loguro: Logging Shouldn't Feel Like Flying a Spaceship 🚀
When I started building Loguro, I had one simple mission: Keep logging simple. That’s it.
Whenever I show it to people, the first thing I hear is: "But we already have Axiom, Datadog, and all these massive solutions." True. But those tools are built for a scale that often brings unnecessary friction. You end up paying for features you don't use, navigating "flight-simulator" dashboards, and learning proprietary query languages just to find a single error.
Loguro is the "no-noise" SaaS alternative. I wanted a tool where the tech stays out of the way so you can focus on the code.
🛠 The Philosophy: Focus on the Code, Not the Tool
The goal for Loguro is to stay out of your way. It is a tool where you don't need to hunt for buttons or navigate complex pages.
1. Human-First Querying
Write filters the way you'd explain them to a colleague. No syntax manuals needed.
| Syntax | What it does | Example |
|---|---|---|
level: |
Filter by severity | level:error |
@ |
Natural time |
@today or @10minutesago
|
from: and to: |
Still natural time | from:"10 days ago" to:"yesterday" |
!message: |
Exclude the noise | !message:"cache miss" |
context. |
Deep-dive fields | context.user_id:42 |
trace. |
Follow a trace send with X-Request-ID header |
trace."uuid" |
2. The "Mouse-Free" Workflow ⌨️
I’m obsessed with keeping you on the keyboard. If you have to reach for your mouse, I’ve failed as a designer.
-
Autocompletion: It’s smart and it’s fast. Hit
Taband it’s there for you. -
Saved Views:
Cmd/Ctrl + Sto save a complex query,Cmd/Ctrl + Bto browse them. -
Command Palette:
Cmd/Ctrl + Kto jump between Logs, API Keys, and Alerts instantly. -
Focused and don't know a query?:
Cmd/Ctrl + /opens the help from the advanced search.
⚡️ Performance that Bites
Don't let the "simple" UI fool you. Under the hood, the engine is a beast:
- Sub-500ms query times on 50M+ logs.
- 45k+ req/s ingestion on single requests.
- 500k+ logs/s in batch mode.
🎯 Key Features at a Glance
- Signal Monitors (Alerts): Set up a per-project alert in 5 clicks from the UI, or 2 clicks directly from a log line you’re currently investigating.
- Trace Discovery: Traces are first-class citizens. Click a trace ID to instantly follow the entire request lifecycle.
-
Log Detail View: One-click copy for Trace IDs, IDs, or the full JSON context. Visual styling changes based on log severity so you can spot errors in a sea of info. Find anything inside the context with the advanced search and jump between entries with just
Enter.
The Vision
Loguro is for the developer who wants to Find the bug. Fix it. Move on. ☕️
I’m constantly adding features to keep the experience as simple and mouse-free as possible. If you've ever felt overwhelmed by the complexity of modern observability, Loguro might be the breath of fresh air you need.
There are a lot of ideas i have in my head waiting for me to put them on Loguro, like:
Secure, "No-Login" Sharing
We've all been there: a Product Owner asks why payments are failing. Instead of taking a sketchy screenshot, Loguro will let you generate a secure, shareable link to a specific log entry or view. They get the context they need; you don't have to manage a new user account for them. Just to let the PO know why the revenue stopped—just saying.
BYOS
There are companies which do not want to store the logs on my servers, or they just want to avoid paying the storage(which BTW is cheap because of the parquet compression i am using), so i shall be able to provide them a way to add credentials for whatever storage provider they want, S3, R2, whatever, and just push the logs there while the queries will still happen on my own dashboard but without me having a single piece of log from them on my server.
What’s the one thing that drives you crazy about your current logging setup? Let’s chat in the comments.
While i still work on it, even if it's fully working at production level, there is only one plan, *FREE with generous limits. Something will change on the future, maybe the retention, but we'll see.
PS. It doesn't need to be used on web only, it can be used in any setup that provides a secure way for you to use an api key, even a plain server on which you need to have some logs and alerts.
You can give it a spin here: loguro
Top comments (0)