Choose your path
OpenTelemetry
Start here for any backend service. Traces, metrics, and logs from the OTel SDK for your language, in any runtime.
Web SDK
For browser apps that need wallet and provider capture, including the steps that never reach your backend.
OpenTelemetry Collector
Already running a Collector? Add Mirador as an exporter and fan out existing pipelines.
REST API
Query traces, logs, and metrics programmatically with a server key.
Send your first trace
Any OpenTelemetry SDK works. Set four standard environment variables and run:Quickstart
Full walkthrough, from API key to a correlated on-chain trace
What makes a Mirador trace different
Enrichment hints
Emit one reserved span event and Mirador follows the transaction through receipt, bridge fill, or payout
Cross-chain correlation
Bridge legs, Safe multisig confirmations, and Solana or Canton transactions joined to the originating flow
Traces, metrics, and logs
All three OTLP signals on one endpoint, isolated per project
Automations
Rules that watch traces and route matches to Slack and other integrations
AI and agents
Connect an agent to investigate flows through the query API
Web3 demo app
A working example with real wallet interactions
Supported signals
Next steps
Pick your language
OTel SDK links and setup for every supported runtime
OpenTelemetry overview
Endpoints, authentication, and Collector configuration
Web SDK
Browser instrumentation and wallet capture
Best practices
Naming, attributes, and sampling guidance