OTel supports multiple signals: tracing, metrics, events (structured logs), will support profiles, and whatnot.
Having individual package for each signal does not make sense:
- complicates onboarding
- packages have the same dependency graph
- package versions need to be aligned
- ...
- most importantly, separating them does not have any clear benefit
We should consider merging them and following otel-like naming pattern opentelemetry-azure-sdk.
It probably may be moved away from azure-core ? (JS puts it https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/instrumentation/opentelemetry-instrumentation-azure-sdk)