← All platforms

Hono error tracking

Small framework. Plenty of places to run it. The Sentry Hono integration sends application errors to Telebugs on your server, wherever your Hono app lives.

~/hoofnotes  npm install @sentry/hono @sentry/node
~/hoofnotes  nvim instrument.mjs app.mjs
import * as Sentry from "@sentry/hono/node";
Sentry.init({
// Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
});
import { Hono } from "hono";
import { serve } from "@hono/node-server";
import { sentry } from "@sentry/hono/node";
import { routes } from "./hoofnotes/routes.mjs";
const app = new Hono();
app.use(sentry(app));
app.route("/notes", routes);
serve(app);
~/hoofnotes  node --import ./instrument.mjs app.mjs

Space pauses or resumes. R replays. Escape shows the complete setup.

Hang on, I already use Sentry

Keep @sentry/hono and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

Does the runtime matter?

The Hono SDK has runtime-specific entry points for Node.js, Bun, Deno, and Cloudflare. Use the matching one. Telebugs remains the destination for the resulting error reports.

What happens when a route fails?

The Hono integration reports the exception with the context it captures from that request. You can also report errors that your own handler catches.