Everything the SDK says about itself (exporter failures, init warnings,
internal catch blocks) goes through here rather than straight to console:
It only reaches the developer console when the SDK is in debug mode
(debug: true or a DebugOptions object in the plugin options, or a
DEBUG=true build). A production page is not filled with
[@launchdarkly/observability] lines the app owner cannot act on.
While it is being written, the console recorder is told to stand down
(see isSdkConsoleOutput), so the line is never captured and shipped
back as one of the customer's own log records. Before this, a failing
OTLP export surfaced as error-level launchdarkly.js.log rows in the
customer's own project.
SDK-internal diagnostics.
Everything the SDK says about itself (exporter failures, init warnings, internal catch blocks) goes through here rather than straight to
console:debug: trueor aDebugOptionsobject in the plugin options, or aDEBUG=truebuild). A production page is not filled with[@launchdarkly/observability]lines the app owner cannot act on.isSdkConsoleOutput), so the line is never captured and shipped back as one of the customer's own log records. Before this, a failing OTLP export surfaced as error-levellaunchdarkly.js.logrows in the customer's own project.