chore: move trace exporters back to experimental

[dyladan]

Move trace exporters back to experimental temporarily while we work on splitting the transformation logic out of the JSON exporter. This will break the experimental build because the exporters depend on the unreleased functionality in core. Once there is a stable release the experimental build will pass again. After we have a working release with the new split transformation logic we can release the proto/grpc exporters as stable.

[codecov]

Codecov Report

Merging #2835 (2ef36b9) into main (549bd5b) will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2835      +/-   ##
==========================================
+ Coverage   93.19%   93.58%   +0.38%     
==========================================
  Files         157      120      -37     
  Lines        5117     4658     -459     
  Branches     1097     1046      -51     
==========================================
- Hits         4769     4359     -410     
+ Misses        348      299      -49     

Impacted Files	Coverage Δ
...s/exporter-trace-otlp-http/src/OTLPExporterBase.ts
...packages/exporter-trace-otlp-http/src/transform.ts
...tal/packages/exporter-trace-otlp-http/src/types.ts
...ntal/packages/exporter-trace-otlp-http/src/util.ts
...etry-sdk-metrics-base/src/state/MetricCollector.ts
.../opentelemetry-sdk-metrics-base/src/Instruments.ts
...-metrics-base/examples/metrics/metrics/observer.js
...es/opentelemetry-sdk-metrics-base/src/view/View.ts
...sdk-metrics-base/src/exemplar/ExemplarReservoir.ts
...telemetry-sdk-metrics-base/src/view/Aggregation.ts
... and 43 more

[dyladan]

Marked as draft until #2836 is merged and a release is cut

[rauno56]

GHA seems to be acting up and not running CI. Perhaps the queues are long or something. Similar problems in contrib.

[Flarna]

I finally got the build green for all node.js versions by using a mix of 1.1.0 and 1.0.0 components. Different NPM versions have a different dedup algorithm. as some experimental components depend on released 0.27.0 versions on NPM it's not possible as of now to get rid of API/SDK 1.0.

Therefore some followup tasks are needed but I would like to do this in different PRs:

• get rid of the @opentelemetry/api-metrics-wip and @opentelemetry/sdk-metrics-base-wip to avoid depending on old releases of them on NPM
• Update dependencies to API/Core and use proper version ranges

[dyladan]

• get rid of the @opentelemetry/api-metrics-wip and @opentelemetry/sdk-metrics-base-wip to avoid depending on old releases of them on NPM

Their package.json fields are marked as private so they have never been released and will never be released with those names. @pichlermarc is currently working on updating the OTLP metrics exporters to use the new data model and @legendecas is updating the prometheus. I believe these are the only modules depending on the metrics api/sdk so the names will be able to be switched back to the "real" names and they can be released as alpha when that is complete.

• Update dependencies to API/Core and use proper version ranges

👍

[Flarna]

I believe these are the only modules depending on the metrics api/sdk so the names will be able to be switched back to the "real" names and they can be released as alpha when that is complete.

dependencies on @opentelemetry/sdk-metrics-base (besides exporters)

• @opentelemetry/otlp-transformer
• @opentelemetry/sdk-node

dependencies on @opentelemetry/api-metrics (besides exporters)

• @opentelemetry/instrumentation
• @opentelemetry/instrumentation-grpc
• @opentelemetry/otlp-transformer
• @opentelemetry/sdk-node

As long as this is not cleaned we get old API/SDK versions into the experimental build.