Honeybadger errors for every product, in one place.
See unresolved errors, occurrences per day, and the busiest errors, for each Honeybadger project, next to the rest of each product.
Your personal Honeybadger auth token. LopeBase lists your projects to pick from.
What LopeBase reads
- Error summaryUnresolved errors per project, and occurrences in the last 24 hours for the busiest ones.
- Busiest errorsThe open errors seen most in the last day, with class, message, and environment.
- Daily occurrencesOccurrences per day for the busiest open errors over the last two weeks.
How to connect it
- 01
Copy your personal auth token from your Honeybadger profile, under Authentication.
- 02
Pick each property's project from the list LopeBase shows.
- 03
Error totals and spikes show next to each product's revenue and traffic.
What LopeBase does with it
LopeBase only reads errors and occurrence counts. It never resolves, assigns, or changes anything in Honeybadger.
- Errors beside revenueEach product's open errors sit on its row, next to its revenue and traffic, so a spike has context.
- A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
- AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Honeybadger questions
Something else? Email us.
Which errors does it count?
Errors that are neither resolved nor ignored, the same as Honeybadger's default view.
Why are daily counts limited to the busiest errors?
Honeybadger reports occurrences per error, so LopeBase adds up the 25 busiest open errors. Rare errors may be left out of the daily chart.
Can I resolve errors from LopeBase?
No. The Honeybadger connector only reads. Resolve errors in Honeybadger.
Put Honeybadger next to everything else.
EmDashFree for one product. No card.