Key Concepts

Projects

A project maps to one of your apps or services. Each project has its own API key and its own event inbox. You can have multiple projects — e.g. one per product or per environment (staging vs. production).

Channels

Channels are free-form labels you choose when logging an event: "signups", "payments", "errors", or anything else. They appear as filterable streams in your inbox. No need to pre-create them — they're created on first use.

Events

An event is a single log entry. Each event has:

• event — short human-readable title (required)
• description — one-liner with context (optional)
• icon — emoji shown in the inbox (optional)
• notify — send a push notification, default false (optional)
• tags — key-value pairs for filtering (optional)
• metadata — arbitrary JSON (optional)
• trackingId — ID of the first event in a timeline, links events together (optional)
• inbox — show this event in the realtime inbox, default true (optional)

API Keys

Each project has one API key. Pass it as the token option in the SDK or as the Authorization: Bearer header for REST calls. Keys are project-scoped — they can only ingest events to that specific project.

Tags & Metadata

Tags are flat key-value strings for filtering in the dashboard. Keep them short and consistent.

Metadata is an arbitrary JSON object — store anything you'd want to see when expanding an event card: user ID, email, amount, stack trace, etc.

await logit.now("payments", {
  event: "Payment received",
  tags: { plan: "pro", currency: "usd" },   // filterable in dashboard
  metadata: {                                // expandable detail view
    userId: "user_abc",
    amount: 49,
    stripeChargeId: "ch_3abc...",
  },
});