laminar-migrate-observability
Installation
SKILL.md
Laminar Migrate Observability
Workflow
- Identify the current provider, runtime, and entrypoints. Capture trace boundaries and existing context (user/session IDs, tags, metadata, redaction rules).
- Choose the migration approach:
- If OpenTelemetry is already in use, keep instrumentation and reconfigure the OTLP exporter to Laminar.
- Otherwise, replace wrappers/decorators with Laminar
observe()/@observe()or manual spans, and enable provider auto-instrumentation. - Avoid double-instrumentation.
- Install Laminar with the repo's package manager. Add
LMNR_PROJECT_API_KEY(and base URL if self-hosted) to env examples. - Map concepts and naming: stable span names, low-cardinality tags, IDs in metadata.
- Verify: run a representative flow and confirm root span, child spans, and tags in the UI. Ensure trace context is preserved end-to-end.
References
references/migration-mapping.mdfor provider-to-Laminar concept mapping and minimal-diff patterns.references/otel-exporter.mdfor OTLP exporter setup guidance.
Related skills
More from lmnr-ai/laminar-skills
laminar-quickstart-trace
Create a minimal Laminar trace demo in minutes with no external LLM calls. Use when a user asks for a Laminar example, a quickstart demo, or wants to see traces appear in the Laminar UI quickly (cloud or self-hosted).
28laminar-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.
25query-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