Telebugs 1.14.4 released.
Posts by Telebugs Error Tracking
Improved the error report view in @telebugs.com. This was long overdue.
Nested errors (the actual cause) now live inside the backtrace:
โ
grouped together
โ
full stack trace (wasnโt available before)
As a side effect:
โ
fewer queries across Reports & Notes
โ
fully cached
Telebugs 1.14.3 released.
Telebugs 1.14.2 released.
๐ฃ The next version of @telebugs.com will support displaying local variables for each stack frame (when available).
"Telebugs never misses anything, the web UI is delightfully efficient and the whole setup took less than an hour from purchase to production."
Just published this heartfelt testimonial for @telebugs.com ๐ฅน
--
I'm building a Sentry alternative for error tracking:
telebugs.com
"After more than 10 years running production systems, Iโve tried countless error tracking tools. Telebugs is the first one that finally feels like a sensible self-hosted solution without unnecessary complexity."
This @telebugs.com testimonial makes me so proud ๐ฅน
Telebugs 1.14.1 released.
โWe switched from Sentryโฆ Being in control of our data and removing a US company from our GDPR subprocessor list was critical.โ
Just got this testimonial for @telebugs.com.
Telebugs is a great fit if you want full control over your error tracking, without relying on big corporations ๐
โTested Sentry and GlitchTipโฆ then stumbled upon Telebugs by chance - and it paid off!โ
Just got this testimonial for @telebugs.com and it made my day ๐
Iโm not building it for everyone
Iโm building it for teams that want real simplicity, self-hosted maintainability and zero overcomplicated setups
Claude can now investigate your @telebugs.com errors automatically!
โ
Fetch error reports
โ
Spot patterns
โ
Run root cause analysis
โ
Create tickets in your tracker
A power user just built unofficial Claude Code skills for it.
Give them a spin:
github.com/zhuravel/tel...
โItโs fast, simple to use, and does exactly what you need without overcomplicating things.โ
Just got this testimonial for @telebugs.com and it made my day ๐
Iโm not building it for everyone. Iโm building it for the ones who value simplicity and speed.
Thatโs the whole point.
Telebugs 1.14.0 is live!
Big usability wins:
โ
Extended filters: last 3/7/28/91 days
โ
Automatic sensitive data scrubbing (passwords, tokens, credit cards)
โ
Sparklines next to every error group
โ
โNotify on every occurrenceโ rule
โ
Dual timezone timestamps
โ
Auto-refresh checkbox
๐๐๐
Telebugs 1.14.0 released.
Filtering sensitive information in @telebugs.com.
The upcoming update will automatically scrub passwords, tokens, API keys, credit cards, and other secrets from error reports (server-side, before they ever hit your database).
I'm really close to shipping a new @telebugs.com version. There are just a few more bugs to iron out before it is ready.
The upcoming version will get a lot of bug fixes, more polish and beautiful sparklines per group ๐
Exciting update for @telebugs.com users!
A community member has built an unofficial MCP server (telebugs-mcp) that lets AI agents query and retrieve error reports from your Telebugs instance.
Super useful for AI-powered debugging. Give it a try! ๐
github.com/jilio/telebu...
๐จ PSA for all @telebugs.com users
If you installed Telebugs using the default installer, manually truncate your Docker logs.
Due to an oversight, the log file is never truncated. A future Telebugs release will cap the log size.
Improved timestamp handling in @telebugs.com.
Projects each have their own timezone, but cross-project views use UTC timestamps.
This was confusing: project views showed local time, while others showed UTC.
Now we display relative time everywhere, and on hover the tooltip shows both (local+UTC).
A few weeks ago, a @telebugs.com user shared a really insightful request that hit home for anyone running critical applications.
Today I added support for sentry-cli v3. In @telebugs.com, itโs used to upload source maps.
I still have ~10 support requests pending, and Iโm sorry to everyone whoโs been waiting. Bad timing: I took a few weeks off, and a lot of tickets came in at once.
Normally, I address issues the same day.
Coming soon to @telebugs.com: sparklines for every error.
Each error has its own occurrence pattern. You can already see that on the error page, but until now, there was no quick way to compare errors side by side and spot what needs attention first.
Coming soon to @telebugs.com:
Sparklines beyond the last 24 hours.
Some users donโt check the dashboard daily and want to compare error volume over a few days (Friday sign-off โ Monday return).
Now you can filter project sparklines by timeframe.
New in the upcoming @telebugs.com: auto-refreshing errors.
I noticed some Telebugs users donโt use notifications at all. They just keep the dashboard open and rely on it to stay on top of errors.
So the next release adds a simple checkbox: auto-refresh, to make the dashboard feel a bit more alive.
While I was away for a few weeks, @telebugs.com accumulated a ridiculous backlog of support requests.
There's a pile to go through before I can proceed with @telesink.com.
Iโve just set up a private @telebugs.com demo instance for the first time in a while (for a potential client). Iโve been deploying them with Kamal.
Usually itโs smooth, but this time I hit a snag:
Telebugs 1.13.0 is here with 3 major features:
1๏ธโฃ Microsoft Teams notifications
2๏ธโฃ One-click opening of backtrace frames in your favorite local editor
3๏ธโฃ Direct links to view or edit code right on your repository host.
Bonus point: lots of bug fixes ๐๐จ
Read more:
telebugs.com/blog/telebug...
Telebugs 1.13.0 released.