Documentation
Instrumentation
Guides
API Reference
ChangelogProject
A project is the top-level container for traces, issues, monitors, artifacts, and settings from your agent or agents. Each project has its own dashboard, API key, and project ID. Use separate projects to isolate environments (dev, staging, prod) or distinct products.Agent
An agent isn’t something you register. It’s a name that appears on a trace, and Lemma uses that name to scope Artifacts, Analytics scorecards, issue grouping, and monitors to the right agent. A trace with no usable agent name still ingests, but nothing agent-scoped has anywhere to attach it. A monitor does not judge that trace.Trace
A trace is one ready agent execution: the conversation, the execution tree of spans, and any errors it produced. Traces are what you search and open on the Traces page, and they’re the raw evidence behind every issue.Issue
An issue is a durable grouped failure pattern inferred from trace evidence. Say the issue was observed in a trace. Statuses are open, in progress, resolved, and dismissed. Lemma analyzes a trace after its conversation goes quiet, or immediately if the trace has no thread ID, then groups repeated evidence so the same bug accumulates supporting traces instead of spawning a new issue every time it recurs. Opening an issue shows you the pattern. Opening a supporting trace shows you the specific run. See Issues for status, priority, and investigation. Detection and grouping are probabilistic. Treat an issue as a hypothesis backed by evidence, not a certainty, and open the supporting traces before you call it confirmed. Alerting follows this issue lifecycle; see Product boundaries.Monitor
A monitor is a continuously running tracker attached to an agent. It examines that agent’s traces and records when a specific event or behavior occurs. The monitor’s description tells it what to look for. A signal monitor records an event. A behavior monitor records a wrong behavior and writes an issue. See Monitors for the dashboard workflow.Artifact
Artifacts are agent-scoped. Provided context is text (or a supported text file) you supply about that agent. Generated artifacts are a versioned understanding document and a decision-flow diagram Lemma builds from traces plus that context. Agent names come from observed traces. Context for an agent is not evidence about another. See Artifacts.Product boundaries
Lemma evaluates production usage from real users. It does not offer offline evaluation. If someone asks about “online eval,” they mean evaluating actual production usage. Incidents and a standalone metrics product are not current surfaces. Failure alerting still follows the issue lifecycle via Slack and webhooks. See Monitors.Related pages
Overview
How a trace moves through detection to become an issue.
Issues
Status, priority, and investigating supporting traces.
Monitors
A continuous tracker for an event or behavior in an agent’s traces.
Artifacts
Agent-scoped context that sharpens detection.
SDK concepts
Trace, span, generation, tool call, and thread.