chore: mark otlp exporters experimental

[dyladan]

Per discussions in SIG mark the otlp exporters as unstable until the trace functionality is split from them.

[codecov]

Codecov Report

Merging #2490 (d8b6c0e) into main (d41fa7b) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2490      +/-   ##
==========================================
- Coverage   93.27%   93.25%   -0.02%     
==========================================
  Files         125      137      +12     
  Lines        4445     5043     +598     
  Branches      931     1067     +136     
==========================================
+ Hits         4146     4703     +557     
- Misses        299      340      +41     

Impacted Files	Coverage Δ
...ages/opentelemetry-exporter-otlp-http/src/types.ts	100.00% <0.00%> (ø)
...lemetry-exporter-otlp-http/src/transformMetrics.ts	95.71% <0.00%> (ø)
packages/opentelemetry-sdk-trace-web/src/types.ts	100.00% <0.00%> (ø)
...-sdk-trace-web/src/enums/PerformanceTimingNames.ts	100.00% <0.00%> (ø)
...entelemetry-sdk-trace-web/src/WebTracerProvider.ts	100.00% <0.00%> (ø)
...ry-context-zone-peer-dep/src/ZoneContextManager.ts	85.18% <0.00%> (ø)
...telemetry-sdk-trace-web/src/StackContextManager.ts	94.28% <0.00%> (ø)
...lemetry-exporter-otlp-http/src/OTLPExporterBase.ts	92.15% <0.00%> (ø)
.../opentelemetry-exporter-otlp-http/src/transform.ts	88.69% <0.00%> (ø)
...es/opentelemetry-context-zone-peer-dep/src/util.ts	100.00% <0.00%> (ø)
... and 3 more

[obecny]

lgtm, there is some failure in karma config thats why the browser tests are failing, maybe path is not updated etc. ?

[vmarchaud]

lgtm, PR need rebase though

[jsuereth]

QQ: Is OTel-js going to support OTLP export when the 1.0 is announced?

[dyladan]

@jsuereth we don't want to release the exporter as 1.0 while it depends on the unfinished metric api/sdk. we are moving it to experimental while the trace functionality is split out of it so the 1.0 is unblocked. the exporter with trace-only will be released as 1.0 when it is ready.

[jsuereth]

@dyladan I guess I'm asking, as a user of OTel ecosystem, are we going to advertise users adopt 1.0 against the unstable receiver for OTEL or are we going to wait to advertise until the OTEL receiver is stable? Not trying to hold up this PR just wanted to understand the implications for when users ask about adopting Otel-JS

[dyladan]

@dyladan I guess I'm asking, as a user of OTel ecosystem, are we going to advertise users adopt 1.0 against the unstable receiver for OTEL or are we going to wait to advertise until the OTEL receiver is stable? Not trying to hold up this PR just wanted to understand the implications for when users ask about adopting Otel-JS

I think it is fine to recommend users use the unstable otlp exporter as long as they understand that they will need to upgrade to the stable trace exporter in the near future.

[tedsuo]

sounds good to me, given that the tracing portion of the exporter is "stable," and changing exporters doesn't create issues in the same way that breaking an API does.