
Building observability products that don’t suck @BetterStackHQ. Rails 💎, Vue, Postgres, Clickhouse.
Prague
Joined January 2010
- Tweets493
- Following1.3K
- Followers260
- Likes27.3K
Tomas Hromada retweeted
RE: @opencode drama — everyone needs at MINIMUM 1x always on agent scanning logs for weird activity starting today if you're not already doing this.
It's honestly a warfare out there and worse than ever before. I'm learning SO MUCH via my @bot security agent as he combs through @BetterStackHQ logs multiple times per day.
Similar to @DHH "we can fix everything", we can SECURE everything!
In addition to this, ask your @bot to scan application logs every 24 hours and actively push patches to protect your app. You’ll be shocked what you find!
Tomas Hromada retweeted
Paged at 3am with nothing but an alert name? Not anymore.
Our AI SRE now investigates the moment an incident is created, not when you open your laptop. By the time you're awake, the root cause analysis is waiting.
Tomas Hromada retweeted
See how to create a routing number that connects you with the current on-call person and lets you report incidents by phone.
It's pencils down, people. Writing code by hand is no longer an economically viable skill for most programmers at most companies. But the future of making software has never been brighter. Don't you dare black pill this beautiful moment! youtu.be/vDjW_dRyKXY?si=6Fsf…
Tomas Hromada retweeted
Here it goes... we launched our first ever game.
- 8 unique dragons with different playstyles
- 20+ unique dice to roll
- Numbers go brrrr
- My wife drew EVERYTHING by hand
Feed the Scorchpot. OUT NOW.
Tomas Hromada retweeted
Sharing our internal "no-bullshit guide to Agentic Engineering" @BetterStackHQ
Link in the thread
why does someone still uses @datadoghq in 2026 - there event based pricing is absolutely ridiculous.
we got ~500$ bill for a month, where we recorded ~168 million of logs and it was just about 40gbish.
I shifted our whole logging infra to @BetterStackHQ , took <1hr, our last month bill was ~45$.
and betterstack mcp is such god tier, datadog mcp is also bad.
Tomas Hromada retweeted
ChatGPT, Claude & Gemini rank the best uptime monitor right now:
🥇 @BetterStackHQ
🥈 @uptimerobot
🥉 @hyperping
4. Uptime Kuma
5. @HetrixTools
Why 👇
Tomas Hromada retweeted
We're heading to WeAreDevelopers World Congress Europe!
If you're in Berlin on July 9–10, stop by Hall 2, Booth 27, to see a radically better approach to observability for modern engineering teams. Meet the team, catch a live demo, and grab some swag.
#WeAreDevelopers #wearedevs #observability
Tomas Hromada retweeted
AI creating @BetterStackHQ dashboards for me 😀
Tomas Hromada retweeted
The lovely folks at @JuicedataInc wrote a guide on monitoring JuiceFS with @BetterStackHQ
Tomas Hromada retweeted
Replying to @austriker27 @sentry
I find @BetterStackHQ a lot easier to navigate
Tomas Hromada retweeted
💡 Better Stack gives you a Slack-native AI SRE agent that investigates incidents across your logs, metrics, traces, errors, and web events.
Tomas Hromada retweeted
Collect logs, traces, and metrics from your clusters with zero code changes via eBPF and auto-instrumentation.
Tomas Hromada retweeted
We use @BetterStackHQ heavily in my company.
It works wonders for us, without them we couldn't possibly fix the production bugs that we get. We have BetterStack set up everywhere, and hands down, the best service for error tracking, error logging, and everything that you need, they have it.
Today, we're making Error Tracking by @BetterStackHQ generally available.
Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it.
What's wrong with error tracking today?
Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle.
And so most teams still end up sampling. Which means missing the exact exception that caused the outage.
The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am.
We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together.
The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click.
The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix.
This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act.
The migration is trivial:
1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code.
2. Point the DSN at Better Stack.
3. Done. Errors flow in. Your dashboards work. Your alerts work.
4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo.
5. Review, merge, close. That's the whole workflow.
The AI angle is real, not a marketing badge.
LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model.
We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters.
Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.
Tomas Hromada retweeted
Thanks to @BetterStackHQ for fixing a bunch of performance issues I reported in their dashboard!
The experience is so much faster now 🤩
My response:
Tomas Hromada retweeted
Today, we're introducing eBPF-based OpenTelemetry tracing alongside a remotely controlled Better Stack Collector. eBPF is ready for prime time. Here's the playbook for adopting it.
What's eBPF?
"extended Berkeley Packet Filter" is a Linux kernel technology that lets you run sandboxed programs inside the kernel safely and efficiently. Thanks to eBPF, you can now instrument your clusters with OpenTelemetry without changing any application code 🤯
The eBPF ecosystem has matured significantly over the past few months and many Better Stack customers are already using it in production.
Until now, deploying eBPF to production has been tricky. We're simplifying it today by bundling the best of the open source eBPF sensors into a single remotely controlled Better Stack collector you can deploy with a single command.
Better Stack collector gives you granular control over what exactly gets instrumented. Get the service map of your cluster, RED metrics for individual services, see network flows, and aggregate your application and system logs out of the box. Without changing any code.
Observability tools are only useful if you actually ingest all relevant data. Today, we're making that simpler and more convenient than ever.
The eBPF OpenTelemetry playbook™ = "Do the easy thing before doing the hard thing"
1. In your staging environment.
2. Deploy the eBPF collector into your distributed cluster.
3. In 98% of cases: Declare victory, your app is now instrumented.
4. In 2% of cases: You notice a particular service has slowed down. For example, the CPU utilization on a high-throughput Redis instance handling millions of operations per second got noticeably higher. Better be safe, so you disable eBPF for this single instance while keeping it enabled for the other 98% of services.
5. If needed, use the OpenTelemetry SDK auto-instrumentation to instrument the last 2% of applications.
Most teams today still start with step 5. If you're revisiting your observability stack, I encourage you to give eBPF a chance: it has matured significantly and is better than you might expect.
Better Stack encourages combining OpenTelemetry traces from the OTel SDK, eBPF, and your frontend. That's the only way to get the clearest picture of what's actually happening in your application.
Want to chat eBPF? Catch me at KubeCon in Amsterdam next week!
Tomas Hromada retweeted
Some evenings in Amsterdam are simply gezellig. On March 26 at 7:00 pm, we’re hosting a beer tasting at Café Struis, the official @BrouwerijtIJ tasting room.
No pitches. No slides. Just award-winning beers brewed under the windmill.
Join us! RSVP link in the thread below ↓
Tomas Hromada retweeted
What do you do when you’re in Amsterdam? You get on a boat!
March 24, 8:30 PM. We’re hosting a private canal cruise for the cloud native crowd.
Cold beers. Dutch snacks. Zero agenda.
Join the Better Stack crew for a night on the water! Link to RSVP below ↓
Tomas Hromada retweeted
Don’t visit our booth. Unless, of course, your observability bill is starting to cost more than your infrastructure. Sound familiar? Let us show you a better way at KubeCon + CloudNativeCon 2026. Stop by booth 892 to meet the team, see the platform in action, and experience our AI SRE firsthand.





















