-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[otlp-transformer] stabilization plan #4582
Labels
never-stale
pkg:otlp-transformer
type:feature-tracking
A feature with sub-issues that need to be addressed
Comments
pichlermarc
added
pkg:otlp-transformer
type:feature-tracking
A feature with sub-issues that need to be addressed
labels
Mar 26, 2024
pichlermarc
added
needs:refinement
This issue needs to be refined/broken apart into sub-issues before implementation
and removed
needs:refinement
This issue needs to be refined/broken apart into sub-issues before implementation
labels
Mar 26, 2024
This was referenced Mar 26, 2024
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stale for 14 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
never-stale
pkg:otlp-transformer
type:feature-tracking
A feature with sub-issues that need to be addressed
Description
The
@opentelemetry/otlp-transformer
package contains utilities to serialize signals data to and from OTLP (binary protobuf) or OTLP (json). As all OTLP exporters depend on this package, stabilization of@opentelemetry/otlp-transformer
is required for exporter stability.The package may be moved to stable once the below issues are resolved.
Currently the following issues prevent stabilization:
Large API surface:
The API surface currently consists of 40+ types and functions. By moving the complete serialization process to
@opentelemetry/otlp-transformer
we will be able to reduce the API surface to an interfaceISerializer
, one serializer implementation per signal (metrics, logs, traces) and type (binary protobuf, json), as well as one response type per signal.Reducing the API surface is required to enable optimizations in the serialization process in terms memory use, performance, and bundle size without being constrained by a large stable public API.
This will be addressed by #4583
Non-stable dependencies:
@opentelemetry/otlp-transformer
depends on@opentelemetry/sdk-logs
and@opentelemetry/api-logs
which may not be stable by the time we want to stabilize the@opentelemetry/otlp-transformer
package. In this case, after reducing the API surface, we should mark all types and functions that use experimental types as@experimental
This will be addressed by #4584
The text was updated successfully, but these errors were encountered: