laminar-quickstart-trace
Laminar Quickstart Trace
Workflow
- Confirm runtime (Node/TS vs Python), Laminar backend target (cloud vs self-hosted), and availability of
LMNR_PROJECT_API_KEY. - Build the smallest runnable demo using manual spans only; tag the trace with a unique run id for easy filtering.
- Run the script and direct the user to the Traces view; filter by tag or metadata to find the trace.
- If traces do not show quickly, retry with batching disabled and call
Laminar.flush().
References
references/quickstart-node.mdfor a Node/JS demo with code and commands.references/quickstart-python.mdfor a Python demo with code and commands.references/troubleshooting.mdfor common failures and fast fixes.
More from lmnr-ai/laminar-skills
laminar-instrument-codebase
Instrument an existing codebase with Laminar tracing: choose which functions to observe, initialize Laminar correctly, add tags/metadata/session IDs, and verify traces. Use when a user asks to add Laminar tracing, instrument functions, or integrate Laminar with a TS/JS or Python codebase.
25laminar-migrate-observability
Migrate an existing observability/tracing setup (Langfuse, LangSmith, Helicone, or OpenTelemetry) to Laminar with minimal diffs. Use when a user wants to replace their current tracer/exporter, keep trace boundaries, or map tags/metadata to Laminar.
10query-api
Use when working with Laminar's SQL Query API (/v1/sql/query): design SELECT-only ClickHouse queries, use parameters, authenticate with project API keys, and interpret response data from spans, traces, events, tags, datasets, and evaluations.
9