feat: add OpenTelemetry support with default no-op adapter #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces OpenTelemetry integration into the
Chargebeexlibrary, enabling users to implement custom span instrumentation for tracing and monitoring. It includes a default no-op implementation and allows configuration of custom adapters. Additionally, OpenTelemetry spans are integrated into theChargebeex.Clientmodule for HTTP request tracing.OpenTelemetry Integration
README.mdexplaining OpenTelemetry integration, including default behavior, custom implementation examples, configuration, and usage.Chargebeex.OpenTelemetry.Defaultthat adheres to the OpenTelemetry behavior, serving as the default adapter.Chargebeex.OpenTelemetry.OpenTelemetryBehaviourmodule, specifying the required callbacks for custom OpenTelemetry adapters.Client Module Enhancements
Chargebeex.Clientmodule forgetandpostmethods, enabling automatic tracing of HTTP requests.otel_adapter/0inChargebeex.Clientto fetch the configured OpenTelemetry adapter, defaulting toChargebeex.OpenTelemetry.Default.