Deno Deploy
A handler wrapper, imported straight from the registry.
Take the write key
Everything this install sends is tagged with it, so one key per environment keeps staging out of your production numbers.
Generating…Install
One package, in the service you are instrumenting.
import from jsr:@clearplane/denoAdd it to Deno Deploy
Paste this where the request path is assembled. The account callback is the only part you have to fill in — it is what turns a request into a customer.
ts
import { withClearplane } from "jsr:@clearplane/deno";
Deno.serve(withClearplane(async (request) => {
return new Response(await handle(request));
}));Name this install
Name it for the deployment rather than the framework. Two Next.js apps in one workspace is the normal case, and “Next.js” twice helps nobody.
Environment
Events land in events_deno_deploy and are queryable from Chat, models, and SQL.