Documentation
Find what happened to a customer
Connect one application, carry customer identity across every signal, and follow the evidence from an error to replay, traces, logs, and a grounded explanation.
01 · Start
See your first customer story
Connect one application, send a test failure, and verify the complete timeline.
Open the quickstart →
02 · Investigate
Understand one customer
Move through their errors, replay, traces, logs, releases, and AI activity in order.
Follow the workflow →
03 · AI agents
Connect your coding agent
Give Claude Code, Cursor, Codex, or another MCP client governed access to evidence.
Connect with MCP →
Browse
Documentation by task
Start with a task, then use reference pages for exact SDK, CLI, configuration, and API details.
Start here
Start here
Connect one application and reach the first complete customer story.
- Quickstart: see your first customer storyConnect one application, identify a test customer, and follow an error across their Teml timeline.
- Choose an integrationPick the shortest supported path for your application and the signals you need.
- Verify your setupConfirm that telemetry and customer identity are connected before expanding your rollout.
Instrument
Instrument
Add identity, errors, traces, replay, events, and AI-call telemetry.
- Identify customersUse one stable customer identity across errors, traces, logs, replay, events, and AI calls.
- JavaScript and TypeScriptInstrument Node.js, browser, Express, and React applications with the Teml SDK.
- PythonInstrument Python services and add request-safe customer identity.
- GoInstrument Go services with traces, logs, errors, and request-scoped customer identity.
- Choose a mobile SDKConnect iOS, Android, React Native, or Flutter activity to the same customer story.
- iOSCapture iOS identity, events, errors, crashes, and backend request context.
- AndroidCapture Android identity, events, errors, crashes, and backend request context.
- React NativeConnect JavaScript and native mobile failures to one React Native customer journey.
- FlutterConnect Dart and native mobile failures to one Flutter customer journey.
- OpenTelemetrySend existing OTLP traces, logs, and metrics to Teml without replacing your instrumentation.
- Capture errors and releasesSend actionable errors, keep grouping useful, and resolve production stack frames.
- Record session replay safelyCapture browser sessions with privacy masking and connect them to errors and backend traces.
- Record LLM callsCapture model, token, latency, error, and cost data and attach it to the customer who caused it.
- Add diagnostic eventsRecord the application milestones that explain what happened before and after a failure.
Investigate
Investigate
Move from a customer or Issue to the evidence that explains it.
- Understand one customer’s storyUse the customer timeline to follow errors, traces, logs, replay, events, and AI activity in order.
- Triage an IssuePrioritize an error by customer impact, reproduce its story, and move it through its lifecycle.
- Investigate with Customer DetectiveAsk production questions and verify grounded answers against cited telemetry.
- Search logs, traces, and metricsUse raw telemetry when a customer story or Issue requires a deeper service-level investigation.
- Investigate service health and dashboardsFind a broad service symptom, follow it into traces and logs, and save only the views worth repeating.
- Inspect events and customer cohortsCheck who performed a diagnostic event and save reusable customer groups for investigation or rollout targeting.
- Investigate accounts and segmentsConnect customers to companies or workspaces and watch important account groups.
- Investigate agent runsTriage AI executions by customer, status, cost, tools, and quality evidence.
- Review detected anomaliesTriage unusual metric behavior, confirm impact, and close findings without mistaking detection for cause.
- Explain LLM spend per customerFind which customers, models, and agent runs are driving cost and failures.
- Check rollout healthConnect feature exposure and releases to the customers and failures that followed.
Respond
Respond
Create actionable alerts and coordinate incidents and on-call.
Manage Teml
Manage Teml
Manage projects, access, connections, notification delivery, and usage.
- Manage a workspace and projectsKeep customer data separated by project and manage organization access safely.
- Connect tools and notification deliveryConnect external tools, create delivery channels, and verify alerts can reach responders.
- Review usage and AI settingsUnderstand plan consumption, retention, LLM pricing, and automatic agent-run checks.
- Save searches and export dataPreserve repeatable filters and create bounded CSV, JSON, or Parquet export jobs.
AI agents
AI agents
Use MCP and the CLI with scoped access and safe actions.
- Connect an AI agent with MCPGive Claude Code, Cursor, Codex, or another MCP client governed access to Teml evidence.
- Use the Teml CLIInvestigate and operate Teml from a terminal or coding agent.
- Permissions and safe actionsScope agent credentials, review evidence, and require confirmation for destructive changes.
Reference
Reference
Look up SDK functions, CLI commands, configuration, authentication, REST, MCP, and limits.
- ConfigurationCommon SDK and OpenTelemetry settings, defaults, and production guidance.
- Authentication and API keysCreate, scope, send, rotate, and revoke Teml credentials safely.
- Permission scopesChoose the least API-key permissions required for ingestion, investigation, response, and administration.
- REST APIUse Teml's public API conventions and find every supported customer resource family.
- JavaScript SDK APIFunctions, classes, options, parameters, and return values for the Teml JavaScript and TypeScript SDK.
- Python SDK APIClasses, methods, parameters, return values, configuration, and integrations for the Teml Python SDK.
- Go SDK APIInterfaces, functions, options, parameters, return values, and helpers for the Teml Go SDK.
- iOS SDK APIFunctions, options, parameters, return values, and propagation helpers for the Teml Swift SDK.
- Android SDK APIFunctions, options, parameters, return values, and propagation helpers for the Teml Kotlin SDK.
- React Native SDK APIFunctions, options, parameters, promises, and native behavior for the Teml React Native SDK.
- Flutter SDK APIFunctions, options, parameters, futures, and native behavior for the Teml Flutter SDK.
- CLI command referenceLook up every Teml CLI command, argument, flag, output convention, and exit code.
- MCP tool referenceUnderstand Teml's MCP tool families and discover the tools available to your key.
- Plans, limits, and retentionUnderstand Teml's planned usage meters and history windows during early access.
Help
Help
Diagnose missing evidence, broken connections, and delivery problems.
- TroubleshootingStart with the symptom and verify project, environment, time, identity, and delivery in order.
- No data is appearingDiagnose missing traces, logs, metrics, errors, events, and replay without changing unrelated settings.
- Customer activity is not connectingFix missing, split, or incorrectly attributed customer timelines.
- Replay or symbols are not workingDiagnose missing browser recordings and unreadable JavaScript, Android, or iOS stack frames.
- Support, security, and privacyContact Teml, report a security issue, and ask for current trust and data-handling information.
- Authentication or access is failingResolve sign-in, API-key, project, and missing-scope failures without widening access unnecessarily.
- MCP or CLI is not workingDiagnose agent connection, CLI authentication, project selection, and safe-write failures.
- Alerts or integrations are not deliveringTrace a missing notification from rule evaluation through channel, connection, and on-call routing.