Installation

Install the package that matches your stack. You can mix and match — for example, @autter/runtime-browser on the frontend with @autter/runtime-node on an Express backend.

npm install @autter/runtime-browser   # frontend (React, Vue, any SPA, static sites)
npm install @autter/runtime-node
npm install @autter/runtime-next

Operation logging requires Node/Next.js SDK and ingester 1.4.0+ (compatibility table), including runtimeLogger, withRuntimeOperation, and the flush APIs. Check the installed exports and deployed ingester/platform before adding logging code; neither latest nor an existing dependency range proves support. See Operation logging.

Frontend
Backend
Next.js

Errors and usage, automatic from init:

import { initAutterBrowser, captureException, trackEvent } from "@autter/runtime-browser";

initAutterBrowser({
  endpoint: "/api/autter-runtime",   // your relay route (recommended), or
  // endpoint: "https://otlp.autter.dev/v1/browser", clientKey: "autter_rtc_…",
  service: "web-app",
  release: import.meta.env.VITE_GIT_SHA,
});

captureException(err, { operation: "start-checkout" });
trackEvent("clicked_upgrade");

React render errors don’t reach window.onerror — wrap your app with the error boundary (import from @autter/runtime-next/client, works in any React app):

import { AutterErrorBoundary } from "@autter/runtime-next/client";

<AutterErrorBoundary fallback={<ErrorPage />}>
  <App />
</AutterErrorBoundary>

Static site with no backend? Deploy the serverless relay and keep endpoint: "/api/autter-runtime" — see Stack integrations. Direct ingest with a client key is a lossy fallback only.

One preloaded file, requests traced automatically:

// instrument.cjs — run with: node --require ./instrument.cjs server.js
const { initAutterServer } = require("@autter/runtime-node");
initAutterServer({
  apiKey: process.env.AUTTER_RUNTIME_KEY,   // secret server key
  service: "payments-api",
  environment: "production",
  release: process.env.GIT_SHA,
  retainTracesAboveMs: 2000,
});

ESM-only app? Use --import plus OpenTelemetry’s loader hook — see the @autter/runtime-node package README.

npm install @autter/runtime-next

Three files give you server tracing, browser tracking, the relay, and the error boundary — instrumentation.ts, app/api/autter-runtime/route.ts, and a client component. See the @autter/runtime-next package README for the exact snippets.Initialize registerAutter from @autter/runtime-next/server inside the Node branch of instrumentation.ts. Server operations/loggers use that same server entry point and require Node; browser components use @autter/runtime-next/client. Do not import server logging APIs into edge routes or client bundles. See Next.js operation logging.

Readable stack traces in production

Minified browser bundles report positions like /assets/index-4f3c.js:1:58213. Upload your build’s source maps with an upload key and the plugin for your bundler, and errors show original files, lines and function names, grouped as one issue across deploys. See Source maps.

Enable endpoint regression telemetry

Reuse existing SDK initialization and pass the options only once. Set release to the deployed commit SHA and use the actual deployment environment. The backend example opts into bounded slow-request retention; the SDK default is off. For Next.js, pass retainTracesAboveMs: 2000 to the existing registerAutter call. The platform rollout does not change installed SDK settings. Self-hosted ingesters need the versions in the compatibility table. See Endpoint regressions for request histogram requirements, trace comparison, team feedback, and draft fix review.

Get a key

Every ingest key is scoped to one orgId + repositoryId. If you’re self-hosting the ingester, generate a key yourself — see Environment variables. If you’re using Autter’s hosted ingester at otlp.autter.dev, create a key from your Autter organization. In the hosted dashboard, open Settings → Access Tokens → Runtime ingest keys → Create key and select the repository. Use a secret server key for OTLP traces/metrics/logs and backend relays; use an origin-restricted client key only for direct browser capture. CLI/PAT and MCP tokens cannot substitute for a Runtime ingest key. Store server keys in your environment or secret manager, without committing or pasting them into agent chat.

Configure diagnostics and operation outcomes

After the capability checks pass, configure the one existing initialization, instrument selected requests/jobs with measured steps and explicit outcomes, and preserve existing loggers. runtimeLogger.error is a diagnostic log; exception capture and failed operation outcomes create issues through traces. Verify stored logs and linked evidence independently, and await logs plus trace/metric flushing before short-lived work ends. Follow the complete Operation logging guide.

No npm in this codebase?

Any language with an OpenTelemetry SDK can send server telemetry with configuration only — no @autter/* package required. See Using Autter Runtime without npm.

Stack integrations

Per-stack setup snippets — React, Node, Next.js, Go, Rust, and any OTel SDK.

Self-hosting

Run the ingester yourself, or point at Autter’s hosted endpoint.

Get started

Guides

Reference