Marc Pichler comments

Results 448 comments of


                                            Marc Pichler

[otlp-transformer] reduce public API surface

Most usages for the types that will be removed are in tests, I'm working on changing the tests so that they are not used anymore. (the start of that is...

[otlp-transformer] reduce public API surface

See also https://github.com/open-telemetry/opentelemetry-js-contrib/issues/2565 for a follow-up in contrib to replace usage of types that will be removed by completing this issue.

Implement Jaeger Remote Sampler as defined by the specification

Thanks for picking this up. It's yours @legalimpurity :slightly_smiling_face:

feat(otlp-transformer): Do not limit `@opentelemetry/api` upper range peerDependency

> Do you happen to have an example for how this is necessary? Example: Adding a new instrument to the `Meter` interface in the API. > I understand that extending...

feat(api): Integrate @opentelemetry/api-logs package into @opentelemetry/api as experimental

> Now that `main` is 2.0, and requires Node 18+, and #5145 will bump TypeScript to 5.0.4, should this be revisited (or closed)? With those technical roadblocks going away, it...

feat(api): Integrate @opentelemetry/api-logs package into @opentelemetry/api as experimental

This PR is blocked on at least https://github.com/open-telemetry/opentelemetry-js/issues/5733 and some other issues https://github.com/open-telemetry/opentelemetry-js/milestone/19. Then we can go ahead and merge the Logs API into `@opentelemetry/api`

Fix password and username in http.url

Thank you for your contribution, this PR was superseded by #5592

improv(tests): add e2e test with collector for all of our OTLP exporters

@JamieDanielson this sounds like a great idea 🙂 I'm adding the blocked label as I'm currently modifying some of the existing tests and I want to ensure that nobody is...

improv(tests): add e2e test with collector for all of our OTLP exporters

@dyladan finished this in #5643

Introduce internal Console API to encapsulate console related calls to manage them from a single point

> > I think the same thing can be achieved by setting a context property when logging that suppresses capture. We do the same thing to suppress tracing our http/grpc...