🐛 Bug Report: Traceloop Init Flag: "Enabled/Disabled"

[nirga]

Description

Currently, OpenLLMetry initializes Traceloop instrumentation automatically without an explicit mechanism to enable or disable it. This behavior may not always align with user needs, such as in cases where instrumentation should be conditionally applied based on environment variables or runtime configurations.

Proposed Feature

Introduce a Traceloop Init Flag that allows users to explicitly enable or disable the instrumentation during initialization. This flag will give users greater control over when Traceloop's features are active in their environment.

Expected Behavior

• A new configuration option (e.g., enabled: true/false) is added to the initialization API or configuration file.
• When enabled is set to false, Traceloop instrumentation is skipped.
• Default behavior should maintain backward compatibility, with the flag set to true by default if not explicitly specified.

Implementation Details

1. Add a new enabled flag in the configuration interface.
2. Update the initialization logic to check the flag before enabling instrumentation.
3. Write unit tests to ensure proper behavior with the flag set to true and false.
4. Update documentation to include details about the new flag.

Use Case

• Development Environments: Developers may want to disable instrumentation in local setups for faster debugging.
• Production Flexibility: Conditional instrumentation can improve performance or meet specific deployment needs.

Impact on Current Users

This change is backward-compatible as the default behavior will continue enabling instrumentation unless the flag is explicitly set to false.