Remix

Loader and action timings, keyed to the account that triggered them.

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/remix

Add it to Remix

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.

tsx

import { withClearplane } from "@clearplane/remix";

export const loader = withClearplane(async ({ request }) => {
  return json(await load(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.

Name

Environment

Events land in events_remix and are queryable from Chat, models, and SQL.