Develop

[ralvescosta]

This pull request refactors the distributed tracing implementation, simplifying the codebase and modularizing the functionality into separate packages. Key changes include the removal of the OTLPTracingBuilder abstraction, the introduction of modular Install methods for OTLP and Noop tracing, and the reorganization of files into distinct packages (amqp, otlp, noop, stdout, and zap).

Refactoring and Modularization:

• Removal of OTLPTracingBuilder abstraction: The otlp.go file was completely rewritten to remove the builder pattern and replace it with a simpler Install function for configuring OTLP tracing. This significantly reduces complexity and improves maintainability. (otlp.go removed in [1] new implementation added in otlp/otlp.go in [2]

• Introduction of modular Install methods: Modular Install methods were introduced for OTLP (otlp/otlp.go) and Noop tracing (noop/noop.go), enabling clear separation and easier integration based on configuration. (noop/noop.go added in [1] otlp/otlp.go added in [2]

File Organization:

• Reorganization into distinct packages: Files were moved into distinct packages such as amqp, otlp, noop, stdout, and zap for better modularization. For example, amqp.go was renamed to amqp/amqp.go, and log.go was renamed to zap/log.go. (amqp/amqp.go renamed in [1] zap/log.go renamed in [2]

Simplification of Tracing Logic:

• Unified tracing installation logic: The Install method in tracing.go now delegates tracing setup to either the OTLP or Noop implementation based on configuration, removing the need for complex builder patterns. (tracing.go modified in tracing.goL10-R21)

New Package Introductions:

• New packages created: Lightweight packages such as stdout and noop were introduced to encapsulate specific tracing implementations. (stdout/stdout.go added in [1] noop/noop.go added in [2]