@latitude-data/telemetry 3.0.0-alpha.0 → 3.0.0-alpha.1

package/README.md

@@ -10,167 +10,467 @@ npm install @latitude-data/telemetry
 
 ## Quick Start
 
+### Bootstrap (Recommended)
+
+The fastest way to start tracing your LLM calls. One function sets up everything:
+
 ```typescript
-import OpenAI from "openai"
-import { LatitudeTelemetry, Instrumentation } from "@latitude-data/telemetry"
+import { initLatitude } from "@latitude-data/telemetry";
 
-const telemetry = new LatitudeTelemetry("your-api-key", "your-project-slug", {
-  instrumentations: {
-    [Instrumentation.OpenAI]: OpenAI,
-  },
-})
+const latitude = initLatitude({
+  apiKey: process.env.LATITUDE_API_KEY!,
+  projectSlug: process.env.LATITUDE_PROJECT_SLUG!,
+  instrumentations: ["openai"], // Auto-instrument OpenAI, Anthropic, etc.
+});
 
-// All OpenAI calls are now automatically traced
-const client = new OpenAI()
-const response = await client.chat.completions.create({
-  model: "gpt-4o-mini",
-  messages: [{ role: "user", content: "Hello!" }],
-})
+// Optionally wait for instrumentations to be ready
+await latitude.ready;
 
-// Ensure traces are sent before process exits
-await telemetry.flush()
+// Your LLM calls will now be traced and sent to Latitude
+const response = await openai.chat.completions.create({
+  model: "gpt-4",
+  messages: [{ role: "user", content: "Hello" }],
+});
+
+await latitude.shutdown();
 ```
 
-## Constructor
+**What this does:**
+
+- Creates a complete OpenTelemetry setup
+- Registers LLM auto-instrumentation (OpenAI, Anthropic, etc.) **asynchronously in the background**
+- Configures the Latitude span processor and exporter
+- Sets up async context propagation (for passing context through async operations)
+
+**Key point about async instrumentations:**
+
+`initLatitude` returns **immediately** — no top-level await needed. Instrumentation registration happens in the background. This avoids top-level await issues in CommonJS environments while still supporting ESM.
+
+- **Fire-and-forget**: Start using your LLM clients right away. Early spans will be captured once instrumentations finish registering.
+- **Optional `await latitude.ready`**: If you want to ensure instrumentations are fully registered before making LLM calls, await the `ready` promise.
+
+**When to use this:** Most applications should start here. It's the simplest path to get LLM observability into Latitude.
+
+**When you might need the advanced setup:**
+
+- You already have OpenTelemetry configured for other backends (Datadog, Sentry, Jaeger)
+- You need custom span processing, sampling, or filtering
+- You want multiple observability backends receiving the same spans
+
+### Existing OpenTelemetry Setup (Advanced)
+
+If your app already uses OpenTelemetry, add Latitude alongside your existing setup:
 
 ```typescript
-new LatitudeTelemetry(apiKey: string, projectSlug: string, options?: TelemetryOptions)
+import { NodeSDK } from "@opentelemetry/sdk-node";
+import {
+  LatitudeSpanProcessor,
+  registerLatitudeInstrumentations,
+} from "@latitude-data/telemetry";
+
+const sdk = new NodeSDK({
+  spanProcessors: [
+    existingProcessor, // Your existing processor
+    new LatitudeSpanProcessor(
+      process.env.LATITUDE_API_KEY!,
+      process.env.LATITUDE_PROJECT_SLUG!,
+    ),
+  ],
+});
+
+sdk.start();
+
+// Enable LLM auto-instrumentation
+await registerLatitudeInstrumentations({
+  instrumentations: ["openai"],
+  tracerProvider: sdk.getTracerProvider(),
+});
+
+// Your LLM calls will now be traced and sent to Latitude
+const response = await openai.chat.completions.create({
+  model: "gpt-4",
+  messages: [{ role: "user", content: "Hello" }],
+});
 ```
 
-| Parameter | Type | Description |
-|-----------|------|-------------|
-| `apiKey` | `string` | Your Latitude API key |
-| `projectSlug` | `string` | Your Latitude project slug |
-| `options` | `TelemetryOptions` | Optional configuration |
+### Why OpenTelemetry?
+
+Latitude Telemetry is built entirely on OpenTelemetry standards. When you're ready to add other observability tools (Datadog, Sentry, Jaeger, etc.), you can use them alongside Latitude without conflicts:
+
+- **Standard span processors** — `LatitudeSpanProcessor` works with any `NodeSDK` or `NodeTracerProvider`
+- **Smart filtering** — Only LLM-relevant spans are exported to Latitude (spans with `gen_ai.*`, `llm.*`, `openinference.*`, or `ai.*` attributes, plus known LLM instrumentation scopes)
+- **Compatible with existing instrumentations** — Works alongside HTTP, DB, and other OTel instrumentations
+- **No vendor lock-in** — Standard OTLP export, no proprietary wire format
+
+## Using `capture()` for Context and Boundaries
+
+The SDK automatically traces LLM calls when you use auto-instrumentation. However, you may want to add additional context (user ID, session ID, tags, or metadata) to group related spans together.
+
+### What `capture()` Does
 
-### Options
+`capture()` wraps your code to attach Latitude context to all LLM spans created inside the callback:
 
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `serviceName` | `string` | `process.env.npm_package_name` | Service name reported in traces |
-| `disableBatch` | `boolean` | `false` | Send spans immediately instead of batching |
-| `exporter` | `SpanExporter` | OTLP to Latitude | Custom span exporter |
-| `processors` | `SpanProcessor[]` | Redact processor | Custom span processors |
-| `propagators` | `TextMapPropagator[]` | W3C Trace + Baggage | Custom context propagators |
-| `instrumentations` | `object` | `{}` | Provider modules to auto-instrument |
+- Adds attributes like `user.id`, `session.id`, `latitude.tags`, and `latitude.metadata` to every span
+- Creates a named boundary for grouping related traces
+- Uses OpenTelemetry's native `context.with()` for reliable async propagation
 
-## Auto-Instrumentation
+### When to Use It
 
-Pass the provider module to automatically instrument all calls:
+You don't need `capture()` to get started—auto-instrumentation handles LLM calls automatically. Use `capture()` when you want to:
+
+- **Group traces by user or session** — Track all LLM calls from a specific user or session
+- **Add business context** — Tag traces with deployment environment, feature flags, or request IDs
+- **Mark agent boundaries** — Wrap an entire agent run or conversation turn with a name and metadata
+- **Filter and analyze** — Use tags and metadata to filter traces in the Latitude
+
+### Example
 
 ```typescript
-import OpenAI from "openai"
-import Anthropic from "@anthropic-ai/sdk"
-import { LatitudeTelemetry, Instrumentation } from "@latitude-data/telemetry"
-
-const telemetry = new LatitudeTelemetry("your-api-key", "your-project-slug", {
-  instrumentations: {
-    [Instrumentation.OpenAI]: OpenAI,
-    [Instrumentation.Anthropic]: Anthropic,
+import { initLatitude, capture } from "@latitude-data/telemetry";
+
+const latitude = initLatitude({
+  apiKey: process.env.LATITUDE_API_KEY!,
+  projectSlug: process.env.LATITUDE_PROJECT_SLUG!,
+  instrumentations: ["openai"],
+});
+
+// Optional: wait for instrumentations before starting
+await latitude.ready;
+
+// Wrap a request or agent run to add context
+await capture(
+  "handle-user-request",
+  async () => {
+    const result = await agent.process(userMessage);
+    return result;
   },
-})
+  {
+    userId: "user_123",
+    sessionId: "session_abc",
+    tags: ["production", "v2-agent"],
+    metadata: { requestId: "req-xyz", featureFlag: "new-prompt" },
+  },
+);
+
+await latitude.shutdown();
 ```
 
-### Supported Providers
+**Important:** `capture()` does not create spans—it only attaches context to spans created by auto-instrumentation. Use one `capture()` call at the request or agent boundary. You can nest calls for granular context; child spans inherit from parent context with local overrides.
 
-| Instrumentation | Package |
-|-----------------|---------|
-| `Instrumentation.OpenAI` | `openai` |
-| `Instrumentation.Anthropic` | `@anthropic-ai/sdk` |
-| `Instrumentation.Bedrock` | `@aws-sdk/client-bedrock-runtime` |
-| `Instrumentation.Cohere` | `cohere-ai` |
-| `Instrumentation.Langchain` | `langchain` |
-| `Instrumentation.LlamaIndex` | `llamaindex` |
-| `Instrumentation.TogetherAI` | `together-ai` |
-| `Instrumentation.VertexAI` | `@google-cloud/vertexai` |
-| `Instrumentation.AIPlatform` | `@google-cloud/aiplatform` |
+## Key Concepts
 
-## Capture
+- **`initLatitude()`** — The primary way to use Latitude. Bootstraps a complete OpenTelemetry setup with LLM auto-instrumentation and the Latitude exporter. Best for most applications.
+- **`LatitudeSpanProcessor`** — For advanced use cases where you already have an OpenTelemetry setup. Exports spans to Latitude alongside your existing observability stack.
+- **`registerLatitudeInstrumentations()`** — Registers LLM auto-instrumentations (OpenAI, Anthropic, etc.) when using the advanced setup with your own provider.
+- **`capture()`** — Optional. Wraps your code to attach Latitude context (tags, userId, sessionId, metadata) to all spans created inside the callback. Use this when you want to group traces by user, session, or add business context.
 
-Use `capture()` to set trace-wide context attributes. All spans created within the callback inherit these as baggage:
+**Important:** Auto-instrumentation traces LLM calls without `capture()`. Use `capture()` only when you need to add context or mark boundaries. Wrap the request, job, or agent entrypoint once—you don't need to wrap every internal step.
+
+## Public API
 
 ```typescript
-await telemetry.capture(
-  {
-    tags: ["production", "chat"],
-    metadata: { environment: "prod", version: "1.2.0" },
-    sessionId: "session-abc-123",
-    userId: "user-456",
-  },
-  async (ctx) => {
-    // All spans created here will carry the tags, metadata, sessionId, userId
-    const response = await client.chat.completions.create({
-      model: "gpt-4o-mini",
-      messages: [{ role: "user", content: "Hello!" }],
-    })
-    return response
-  },
-)
+import {
+  initLatitude,
+  LatitudeSpanProcessor,
+  capture,
+  registerLatitudeInstrumentations,
+} from "@latitude-data/telemetry";
 ```
 
-### Capture Options
+### `initLatitude(options)`
 
-| Option | Type | OTel Attribute | Description |
-|--------|------|----------------|-------------|
-| `tags` | `string[]` | `latitude.tags` | Tags for filtering traces |
-| `metadata` | `Record<string, unknown>` | `latitude.metadata` | Arbitrary key-value metadata |
-| `sessionId` | `string` | `session.id` | Group traces by session |
-| `userId` | `string` | `user.id` | Associate traces with a user |
+The primary entry point. Bootstraps a complete OpenTelemetry setup with LLM instrumentations and Latitude export.
 
-## Custom Spans
+```typescript
+type InitLatitudeOptions = {
+  apiKey: string;
+  projectSlug: string;
+  instrumentations?: InstrumentationType[]; // ["openai", "anthropic", etc.]
+  serviceName?: string;
+  disableBatch?: boolean;
+  disableSmartFilter?: boolean;
+  shouldExportSpan?: (span: ReadableSpan) => boolean;
+  blockedInstrumentationScopes?: string[];
+  disableRedact?: boolean;
+  redact?: RedactSpanProcessorOptions;
+  exporter?: SpanExporter;
+};
+
+function initLatitude(options: InitLatitudeOptions): {
+  provider: NodeTracerProvider; // Access to underlying provider for advanced use
+  ready: Promise<void>; // Resolves when instrumentations are registered
+  flush(): Promise<void>;
+  shutdown(): Promise<void>;
+};
+```
 
-The SDK exposes the underlying OpenTelemetry `tracer` for creating custom spans:
+### `LatitudeSpanProcessor`
+
+Span processor for shared-provider setups. Reads Latitude context from OTel context and stamps attributes onto spans.
 
 ```typescript
-// Simple span
-const span = telemetry.tracer.startSpan("my-operation")
-span.setAttribute("custom.key", "value")
-span.end()
-
-// Nested spans with context
-telemetry.context.with(
-  telemetry.tracer.startSpan("parent").context,
-  () => {
-    const child = telemetry.tracer.startSpan("child")
-    child.end()
-  },
-)
+class LatitudeSpanProcessor implements SpanProcessor {
+  constructor(
+    apiKey: string,
+    projectSlug: string,
+    options?: LatitudeSpanProcessorOptions,
+  );
+}
+
+type LatitudeSpanProcessorOptions = {
+  disableBatch?: boolean;
+  disableSmartFilter?: boolean;
+  shouldExportSpan?: (span: ReadableSpan) => boolean;
+  blockedInstrumentationScopes?: string[];
+  disableRedact?: boolean;
+  redact?: RedactSpanProcessorOptions;
+  exporter?: SpanExporter;
+};
+```
+
+### `capture(name, fn, options?)`
+
+Wraps a function to attach Latitude context to all spans created inside. Uses OpenTelemetry's native `context.with()` for scoping.
+
+```typescript
+type ContextOptions = {
+  name?: string;
+  userId?: string;
+  sessionId?: string;
+  tags?: string[];
+  metadata?: Record<string, unknown>;
+};
+
+function capture<T>(
+  name: string,
+  fn: () => T | Promise<T>,
+  options?: ContextOptions,
+): T | Promise<T>;
+```
+
+**Nested `capture()` behavior:**
+
+- `userId`: last-write-wins
+- `sessionId`: last-write-wins
+- `metadata`: shallow merge
+- `tags`: append and dedupe while preserving order
+
+### `registerLatitudeInstrumentations(options)`
+
+Registers patch-based AI SDK instrumentations against a specific tracer provider.
+
+```typescript
+type InstrumentationType =
+  | "openai"
+  | "anthropic"
+  | "bedrock"
+  | "cohere"
+  | "langchain"
+  | "llamaindex"
+  | "togetherai"
+  | "vertexai"
+  | "aiplatform";
+
+function registerLatitudeInstrumentations(options: {
+  instrumentations: InstrumentationType[];
+  tracerProvider: TracerProvider;
+  instrumentationModules?: Partial<Record<InstrumentationType, unknown>>;
+}): Promise<void>;
+```
+
+## Vendor-Specific Integration Guides
+
+For users with existing observability infrastructure.
+
+### With Datadog
+
+Use Datadog's OTel `TracerProvider` with `LatitudeSpanProcessor`:
+
+```typescript
+import tracer from "dd-trace";
+import { LatitudeSpanProcessor } from "@latitude-data/telemetry";
+
+const ddTracer = tracer.init({ service: "my-app", env: "production" });
+const provider = new ddTracer.TracerProvider();
+
+provider.addSpanProcessor(
+  new LatitudeSpanProcessor(
+    process.env.LATITUDE_API_KEY!,
+    process.env.LATITUDE_PROJECT_SLUG!,
+  ),
+);
+
+provider.register();
+
+// LLM calls are now traced and sent to both Datadog and Latitude
 ```
 
-## Context Management
+**Adding context:** Use `capture()` if you want to add user IDs, session IDs, or tags to your traces (see [Using `capture()` for Context and Boundaries](#using-capture-for-context-and-boundaries)).
+
+### With Sentry
+
+Use Sentry's custom OpenTelemetry setup with `skipOpenTelemetrySetup: true`:
 
 ```typescript
-// Get the current active context
-const ctx = telemetry.context.active()
-
-// Run code within a specific context
-telemetry.context.with(ctx, () => {
-  // spans created here are children of ctx
-})
-
-// Resume a trace from W3C traceparent
-const ctx = telemetry.context.resume({
-  traceparent: "00-trace-id-span-id-01",
-  baggage: "key=value",
-})
+import * as Sentry from "@sentry/node";
+import {
+  SentrySpanProcessor,
+  SentrySampler,
+  SentryPropagator,
+} from "@sentry/opentelemetry";
+import { NodeTracerProvider } from "@opentelemetry/sdk-trace-node";
+import {
+  LatitudeSpanProcessor,
+  registerLatitudeInstrumentations,
+} from "@latitude-data/telemetry";
+
+// Initialize Sentry with custom OTel setup flag
+const sentryClient = Sentry.init({
+  dsn: process.env.SENTRY_DSN,
+  skipOpenTelemetrySetup: true,
+  tracesSampleRate: 1.0,
+});
+
+// Create a shared provider with both Sentry and Latitude processors
+const provider = new NodeTracerProvider({
+  sampler: sentryClient ? new SentrySampler(sentryClient) : undefined,
+  spanProcessors: [
+    new SentrySpanProcessor(), // Send spans to Sentry
+    new LatitudeSpanProcessor(
+      process.env.LATITUDE_API_KEY!,
+      process.env.LATITUDE_PROJECT_SLUG!,
+    ), // Send spans to Latitude
+  ],
+});
+
+// Register with Sentry's propagator and context manager
+provider.register({
+  propagator: new SentryPropagator(),
+  contextManager: new Sentry.SentryContextManager(),
+});
+
+// Add LLM instrumentations
+await registerLatitudeInstrumentations({
+  instrumentations: ["openai"],
+  tracerProvider: provider,
+});
+
+// Validate the setup
+Sentry.validateOpenTelemetrySetup();
+
+// LLM calls are now traced and sent to both Sentry and Latitude
 ```
 
-## Lifecycle
+**Adding context:** Use `capture()` if you want to add user IDs, session IDs, or tags to your traces (see [Using `capture()` for Context and Boundaries](#using-capture-for-context-and-boundaries)).
+
+**Required Sentry packages:** `@sentry/node`, `@sentry/opentelemetry`
+
+**Note:** See [Sentry's custom OTel setup documentation](https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/custom-setup/) for version-specific details.
+
+## Supported AI Providers
+
+| Identifier     | Package                           |
+| -------------- | --------------------------------- |
+| `"openai"`     | `openai`                          |
+| `"anthropic"`  | `@anthropic-ai/sdk`               |
+| `"bedrock"`    | `@aws-sdk/client-bedrock-runtime` |
+| `"cohere"`     | `cohere-ai`                       |
+| `"langchain"`  | `langchain`                       |
+| `"llamaindex"` | `llamaindex`                      |
+| `"togetherai"` | `together-ai`                     |
+| `"vertexai"`   | `@google-cloud/vertexai`          |
+| `"aiplatform"` | `@google-cloud/aiplatform`        |
+
+## Context Options
+
+`capture()` accepts these context options:
+
+| Option      | Type                      | OTel Attribute          | Description                  |
+| ----------- | ------------------------- | ----------------------- | ---------------------------- |
+| `name`      | `string`                  | `latitude.capture.name` | Name for the capture context |
+| `tags`      | `string[]`                | `latitude.tags`         | Tags for filtering traces    |
+| `metadata`  | `Record<string, unknown>` | `latitude.metadata`     | Arbitrary key-value metadata |
+| `sessionId` | `string`                  | `session.id`            | Group traces by session      |
+| `userId`    | `string`                  | `user.id`               | Associate traces with a user |
+
+## Configuration Options
+
+### Smart Filtering
+
+By default, only LLM-relevant spans are exported:
 
 ```typescript
-// Force flush pending spans
-await telemetry.flush()
+new LatitudeSpanProcessor(apiKey, projectSlug, {
+  disableSmartFilter: true, // Export all spans
+});
+```
+
+### Redaction
 
-// Shutdown (flushes then closes)
-await telemetry.shutdown()
+PII redaction is enabled by default for security-sensitive attributes only:
+
+**Redacted by default:**
+
+- HTTP authorization headers
+- HTTP cookies
+- HTTP API key headers (`x-api-key`)
+- Database statements
+
+```typescript
+new LatitudeSpanProcessor(apiKey, projectSlug, {
+  disableRedact: true, // Disable all redaction
+  redact: {
+    attributes: [/^password$/i, /secret/i], // Add custom patterns
+    mask: (attr, value) => "[REDACTED]",
+  },
+});
+```
+
+### Custom Filtering
+
+```typescript
+new LatitudeSpanProcessor(apiKey, projectSlug, {
+  shouldExportSpan: (span) => span.attributes["custom"] === true,
+  blockedInstrumentationScopes: ["opentelemetry.instrumentation.fs"],
+});
 ```
 
 ## Environment Variables
 
-| Variable | Default | Description |
-|----------|---------|-------------|
+| Variable                 | Default                                                             | Description            |
+| ------------------------ | ------------------------------------------------------------------- | ---------------------- |
 | `LATITUDE_TELEMETRY_URL` | `http://localhost:3002` (dev) / `https://ingest.latitude.so` (prod) | OTLP exporter endpoint |
 
+## Troubleshooting
+
+### Spans not appearing in Latitude
+
+1. **Check API key and project slug** — Must be non-empty strings
+2. **Verify instrumentations are registered** — Use `await registerLatitudeInstrumentations()`
+3. **Flush before exit** — Call `await latitude.flush()` or `await provider.forceFlush()`
+4. **Check smart filter** — Only LLM spans are exported by default. Use `disableSmartFilter: true` to export all spans
+5. **Ensure `capture()` wraps the code that creates spans** — `capture()` itself doesn't create spans; it only attaches context to spans created by instrumentations
+
+### No spans created inside `capture()`
+
+`capture()` only attaches context. You need:
+
+1. An active instrumentation (e.g., `@traceloop/instrumentation-openai`)
+2. That instrumentation to create spans for the operations inside your callback
+
+### Context not propagating
+
+Ensure you have a functioning OpenTelemetry context manager registered:
+
+```typescript
+import { AsyncLocalStorageContextManager } from "@opentelemetry/context-async-hooks";
+import { context } from "@opentelemetry/api";
+
+context.setGlobalContextManager(new AsyncLocalStorageContextManager());
+```
+
+`initLatitude()` does this automatically. For shared-provider setups, your app's existing OTel setup should already have this.
+
 ## License
 
 MIT