Platform
- Issues: Open an occurrence explains how See conversation opens that trace.
Platform
- Monitors: Monitors explains a continuous tracker, how to describe what it should find, and what to do when a trace is wrong.
Reference
- Monitor contract: Monitor contract lists agent scope, corrections, learning, and the project board.
Guides
- Analytics query: Querying analytics explains the query body and response, with volume, tool-failure, model-cost, errors-by-agent, and join examples for REST and MCP.
- Analytics skill: Querying analytics opens with how to install the
lemma-analyticsskill so a coding agent can answer volume, latency, tool-failure, and cost questions.
Reference
- Analytics query API: Analytics query API lists every analytics event and field, request key, limit, error, and preset view.
Platform
- Analytics: The Analytics page points to Querying analytics and the analytics skill.
Changelog
- Platform: The platform changelog lists user-facing product changes by day.
- SDKs: The TypeScript SDK and Python SDK changelogs list changes by version.
- Docs: This page lists documentation changes by day.
Reference
- Ingest status: The trace contract says ingest keeps exact
OKandERROR, ignores every other value, and lets a non-empty error forceERROR.
Getting started
- Page titles: Page titles name the task. The introduction title is “Production monitoring for AI agents.”
Guides
- From issue to fix: Turning issues into fixes walks one production issue from the evidence through a code change and a check that it does not recur.
Platform
- Issues: The issues and overview pages link that guide.
Guides
- Runnable examples: Runnable examples points at one docs-chat agent implemented for each first-party stack, plus a direct SDK path.
Integrations
- Wiring: The LangChain, LangGraph, Mastra, OpenAI Agents, and Vercel AI SDK pages show the handler, exporter, or telemetry helper for that example.
Tracing
- Cross-process turns: Cross-process turns explains how a host and a sandbox record one trace.
- Fail open: The traces page says automatic SDK delivery catches network errors, and
ingest()still raises.
Platform
- Product pages: Platform and connection pages match the public product: workspace sequence, ready traces, and the coding-agent setup path.
Connections
- Webhooks and MCP: Webhook and MCP pages replace the previous incident and monitor copy.
Navigation
- Page menu: Each page can be copied, opened as markdown, sent to the docs MCP, or opened in Cursor or Claude Code.
- Introduction: The introduction screenshot sits under the opening paragraph.
Tracing
- Inputs and outputs: Integration pages and the trace contract say prompts, tool payloads, model output, and error messages are always recorded.
Reference
- Analytics attributes: Analytics telemetry lists the generation attributes the SDK emits, and the generations page documents them.
Tracing
- Tool messages: Tool calls documents
userFacingMessageanduser_facing_message.
Tracing
- One delivery: Traces, context, and troubleshooting say each execution sends one complete trace.
TraceHandle.flushis no longer documented. - Second delivery: Troubleshooting describes a root whose input and output are null after a second delivery.
Guides
- Quality guide: Building high-quality traces lives under Guides.
Reference
- Trace contract: The trace contract specifies what clients send and which fields unlock product behavior. The undocumented environment field is gone from the contract.
Guides
- Quality: A guide covers what makes a trace useful to Lemma.
- Migrations: Guides cover moving from Raindrop, Langfuse, and OpenTelemetry.
Getting started
- Public docs: The docs site opens with an introduction and the tracing skill install path.
Tracing
- Instrumentation: Tracing pages cover setup, traces, generations, tool calls, spans, and context.
Integrations
- First-party stacks: Pages cover LangChain, OpenAI Agents, and the Vercel AI SDK.