[draft] otel SDK compatibility

[sfc-gh-pmardziel]

Description

Need to make our otel system compatible with otel SDK.

Other details good to know for developers

Please include any other details of this change useful for TruLens developers.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• New Tests
• This change includes re-generated golden test results
• This change requires a documentation update

---

Important

Add experimental OTEL integration examples for TruLens, including configuration, dummy script, and dependencies.

• Examples:
  • Add Makefile for running OTEL with environment variables and command line arguments, starting/stopping Zipkin and collector.
  • Add dummy.py to demonstrate OTEL integration with TruLens, including setting tracer provider and feedback functions.
  • Add otel-collector-config.yaml for OTEL SDK configuration.
  • Add README.md for OTEL configuration instructions.
• Dependencies:
  • Add requirements.txt with OTEL and related dependencies.

^{This description was created by for eba8628. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to eba8628 in 18 seconds

More details

• Looked at 229 lines of code in 5 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. examples/experimental/otel/Makefile:35

• Draft comment:
  Ensure that otel-collector-config.yaml is in the current directory when running start_collector, or specify the full path to the file.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The Makefile uses a Docker volume mount for the otel-collector-config.yaml file, but it assumes the file is in the current directory. This might cause issues if the file is not present or if the command is run from a different directory.

2. examples/experimental/otel/Makefile:45

• Draft comment:
  The stop_zipkin target stops all containers with the ancestor openzipkin/zipkin. Consider stopping only the specific container by name to avoid affecting other containers.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The stop_zipkin target in the Makefile uses a command that stops all containers with the ancestor openzipkin/zipkin. This could unintentionally stop multiple containers if more than one is running.

3. examples/experimental/otel/dummy.py:7

• Draft comment:
  dotenv is imported but not listed in requirements.txt. Add it to ensure it's installed.
• Reason this comment was not posted:
  Comment did not seem useful.

4. examples/experimental/otel/dummy.py:35

• Draft comment:
  Avoid using broad exceptions. Catch specific exceptions to handle only expected errors.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The dummy.py script uses a try-except block to print a message if no tracer provider is set, but it uses a broad exception clause which is not a best practice.

5. examples/experimental/otel/dummy.py:47

• Draft comment:
  Consider providing instructions or conditions for when to use the commented-out Zipkin exporter setup code.
• Reason this comment was not posted:
  Confidence changes required: 30%
  In dummy.py, the commented-out code for setting up the Zipkin exporter and session with exporter might be useful for users. Consider providing instructions or conditions under which this code should be used.

Workflow ID: wflow_I29yAd6ExY3TSU0O

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.