fix(tracing): otel log level setup only for non-standalone processor

[galkleinman]

Important

Moves OpenTelemetry log level setup in initialize() to occur only when tracing is enabled, preventing setup for standalone processors.

• Behavior:
  • Moves OpenTelemetry log level setup inside the if block checking options.tracingEnabled in initialize() in index.ts.
  • Ensures log level setup only occurs when tracing is enabled, preventing setup for standalone processors.

^{This description was created by for 28e4165. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 28e4165 in 1 minute and 35 seconds. Click for details.

• Reviewed 32 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. packages/traceloop-sdk/src/lib/configuration/index.ts:82

• Draft comment:
  Log level setup is now inside the tracingEnabled block. Ensure this is intentional, as logger configuration won’t occur if tracing is disabled.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

2. packages/traceloop-sdk/src/lib/configuration/index.ts:72

• Draft comment:
  Removed diag.setLogger call from outside the tracing block. Ensure that it’s intended to skip OTEL logging when tracing is disabled.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

3. packages/traceloop-sdk/src/lib/configuration/index.ts:82

• Draft comment:
  Diag logger is now initialized inside the tracingEnabled condition. Confirm that OTEL logging should only be set when tracing is enabled and update docs if needed.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

Workflow ID: wflow_Md0HWP1Mynu7FBZC

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}