Uh oh!
There was an error while loading. Please reload this page.
feat: Remove Otel from fsIntegration - #21654
Conversation
Uh oh!
There was an error while loading. Please reload this page.
mydea
commented
Jun 19, 2026
Ah, simpler (better?) times... |
| recordErrorMessagesAsSpanAttributes: options.recordErrorMessagesAsSpanAttributes, | ||
| }), | ||
| )(); | ||
| if (options.enabled === false) return; |
There was a problem hiding this comment.
m: Do we need to expose an enabled flag? Afaik we don't have such a flag for other instrumentations and not sure if we need it given that the integration needs to be explicitly added
There was a problem hiding this comment.
Ah, because I removed InstrumentationConfig I assumed we needed to retain the enabled to make the change non-breaking but it wasn't exported!
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@opentelemetry/instrumentation-fsto orchestrion #20750This PR doesn't actually use orchestrion.
Becuase
fsin a Node built-in, it is CJS and can therfore be monkey patched like it's 2005.