Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Collectors

For local development, run any OTLP HTTP collector and point both browser and Worker telemetry at it.

The endpoint should accept:

  • POST /v1/traces
  • POST /v1/logs
  • POST /v1/metrics

For browser telemetry, configure CORS on the collector or proxy through your app. For Worker telemetry, use Wrangler secrets for authorization headers and avoid putting tokens in client-side code.

Span names

Useful span names:

  • effect-workerd.Entry.fetch
  • liminal.Client.acquire
  • liminal.Client.listen
  • liminal.Client.send
  • liminal.Client.fn
  • liminal.Client.enqueue-event
  • liminal.ClientDirectory.register
  • liminal.ClientDirectory.unregister
  • liminal.Actor.all.send
  • liminal.Actor.all.disconnect
  • liminal.Actor.others.send
  • liminal.Actor.others.disconnect
  • liminal.workerd.WorkerdActorNamespace.upgrade
  • liminal.workerd.WorkerdActorRuntime.hydrate
  • liminal.workerd.WorkerdActorRuntime.fetch
  • liminal.workerd.WorkerdActorRuntime.socket-message
  • liminal.workerd.WorkerdActorRuntime.socket-close
  • liminal.workerd.WorkerdActorRuntime.socket-error
  • liminal.workerd.WorkerdActorRuntime.handler
  • liminal.workerd.WorkerdActorRuntime.send
  • liminal.workerd.WorkerdActorRuntime.disconnect
  • liminal.workerd.WorkerdActorRuntime.fn-internal

Attributes

Useful attributes:

  • _tag: method or event tag
  • client: Liminal client service id
  • liminal.session.id: durable socket-session id, persisted through hibernation
  • liminal.link: session or transport
  • liminal.transport: websocket, worker, or durable-object-fetch
  • package: liminal or effect-workerd
  • module: instrumentation source module