Introduction

How it works

• Ingest API — Your app sends events, errors, and sessions to the API (e.g. POST /ingest/event).
• SDKs — Platform-specific packages (@tacko/telemetry-next, @tacko/telemetry-node, etc.) or the core library (@tacko/telemetry-core) handle init, batching, and sending.
• Dashboard — Overview, errors, events, and sessions with filters by app and time range.

Quick start (any platform)

Install @tacko/telemetry-core (or the platform package), then call init() with your ingest URL and app name. In the browser, uncaught errors and unhandled promise rejections are reported automatically after init(). Data appears in the dashboard under that app name.

import { init, trackEvent, trackError, screen, identify } from "@tacko/telemetry-core";

init({
  ingestUrl: "https://your-api.example.com",
  app: "my-app",
});

trackEvent("button_click", { id: "submit" });
trackError(new Error("Something broke"), { page: "/checkout" });
screen("/home");
identify("user-123");

Platforms

• Next.js— Provider, error boundary, page tracking, and (via core) global browser error/rejection handlers.
• Nuxt— Plugin + middleware using @tacko/telemetry-core.
• Node.js— Global error handlers, optional request middleware.
• React Native— Global error handler, session and screen tracking.

Identity and anonymous ID

The SDK generates a stable anonymous device id on first init() and sends it (and the SDK version) with every event, error, and session. When you call identify(userId), the same anonymous id is still sent so the backend can link pre-login activity to the user. In the dashboard, a single Identity column shows the user id when set, otherwise the anonymous id.