can't use logfire within durable objects

[samuelcolvin]

I get

✘ [ERROR] Uncaught Error: Config is undefined. This is a bug in the instrumentation logic Error

      at startSpan
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/otel-cf-workers/src/tracer.ts:59:22)
      at startSpan
  (file:///Users/samuel/code/paig-console/node_modules/@opentelemetry/api/src/trace/ProxyTracer.ts:41:30)
      at k
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/logfire-api/dist/index.js:370:19)
      at h
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/logfire-api/dist/index.js:410:3)
      at Te
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/logfire-api/dist/index.js:431:3)
      at acquire (file:///Users/samuel/code/paig-console/worker/src/index.ts:73:15)

[samuelcolvin]

looks like they should work, we just need to document how to do it

https://github.com/pydantic/otel-cf-workers/blob/9e080161f587962db888a8ee00fb5b5432e4b21b/README.md?plain=1#L63

[samuelcolvin]

Okay, i tried to use instrumentDO, but I get

✘ [ERROR] Uncaught TypeError: Failed to construct 'DurableObjectBase': constructor parameter 1 is not of type 'DurableObjectState'. Error

      at RawConcurrencyLimiterDO (file:///Users/samuel/code/paig-console/worker/src/index.ts:67:1)
      at createDO
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/otel-cf-workers/src/instrumentation/do.ts:215:12)
      at with
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/otel-cf-workers/src/context.ts:241:34)
      at with
  (file:///Users/samuel/code/paig-console/node_modules/@opentelemetry/api/src/api/context.ts:77:38)
      at construct
  (file:///Users/samuel/code/paig-console/node_modules/@pydantic/otel-cf-workers/src/instrumentation/do.ts:217:30)

[oxcafedead]

Yes, this is relevant. If workers use Durable Objects in a "new" way (extends vs implements), the code just crashes.

Had do make a workaround and turn off DO instrumentation completely for now.

BTW, the original library otel-cf-workers had this fixed, but this lib was forked before it...

[petyosi]

@oxcafedead When we were forking from the original, I've been exploring the fix with the author, but back then it was quite the rabbit hole.