Honeybadger vs. BugSnag
Developers love Honeybadger for our simple user interface, powerful features, and stellar support.
Simple, predicatable pricing
Tired of confusing pricing schemes? Honeybadger's pricing is transparent and forgiving. We don't charge for overages or extra users, and if you accidentally exceed your monthly plan limits (it happens), just email us—we'll absorb the cost.
“One weekend we sent them 100,000 errors and just got a polite email. Class act.”
—Mike Perham, Creator of Sidekiq and Faktory
Sweta: We’re gearing up for a big product launch in a week and we hit our limit from doing some load testing. We do need exceptions through the rest of the month. What do you advise here?
Josh: Hi Sweta, I've suspended limit checks on your account for the rest of this month, so you shouldn't get cut off if you go over your limit. Just go easy on us. 😁
If you need more errors regularly, I'd recommend upgrading to one of our higher-volume plans.
Good luck with the launch!
Sweta: Wow Josh, thanks SO MUCH!! You and I are on the same team, hope the volume isn’t MUCH higher hahah. Happy weekend!
Your observability toolkit
Quickly answer any question with BadgerQL. Slowest requests today? Most common errors? Who signed up last weekend? BadgerQL is a powerful query language that lets you slice and dice your application data—including your errors!
Everything you need to keep prod running smoothly
Are you paying for features you don't use? We get it. As full-stack developers ourselves, we built the platform that we wanted to use. That's why Honeybadger includes everything you need—and nothing you don't.
Here's a breakdown of BugSnag's features vs. Honeybadger's:
| Honeybadger | BugSnag | |
|---|---|---|
| Midrange Price | $139/mo | $170/mo |
| App Stability Management | ||
| Real User Monitoring | ||
| Error Tracking | ||
| Performance Monitoring | ||
| Uptime Monitoring | ||
| Status Pages | ||
| Cron & Heartbeat Monitoring | ||
| Log Management | ||
| # Errors | 300K/mo | 300K/mo |
| # Telemetry events | 2GB/day ingest | 30M Monthly Spans |
| # Users | unlimited | unlimited |
| Error Retention | 90 days | 60 days |
You've never experienced support like this.
We pride ourselves on giving our customers the best developer-led support in the industry. Go ahead and email us right now—you'll get a fast reply from our dev team, and we'll go above and beyond to answer your questions.
Ben Curtis
To: Jason Charnes
Subject: Re: Uploading logs
Happy to help! And thanks for letting me know it (mostly) worked. I guess I have some debugging to do on that environment variable. :)
One last thing... make sure you run this to get Vector to start after a reboot:
sudo systemctl enable vector.service
I put that in the gist after I sent the last email to you, so you may have done that already, but you may not have, and it doesn't hurt to do it twice. :)
Oh, and about the log prefix you mentioned... look in config/environments/production.rb for config.log_tags and comment that out. That's probably what's adding that stuff to your logs.
Jason Charnes
To: Honeybadger Support
Subject: Re: Uploading logs
That did the trick!!
This is so awesome. Again, thank you!
Get monitoring done.
See the bigger picture, put everything into context & detect anomalies before they become catastrophes.
