Azure Functions
A hook registered once in the app's entry file.
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.
npm i @clearplane/azure-functionsAdd it to Azure Functions
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 { registerClearplane } from "@clearplane/azure-functions";
registerClearplane({ writeKey: process.env.CLEARPLANE_KEY });
app.http("api", { handler });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_azure_functions and are queryable from Chat, models, and SQL.