Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: added support for Opentelemetry 0.18 (#1234)
* fix: added support for Opentelemetry 0.18 Introduces support for Opentelemetry 0.18 API which implements the Tracing 1.0 specification. * style: remove unused import declaration * refactor: removed the `OpenTelemetryTracer`-class and just expose createSpan as function * test: updated the span related tests * test: updated the tests * test: updated the tests * refactor: move the tracer out of the `createSpan`-function Small refactor to ensure no new tracer gets created for each call to the `createSpan`-functio by initiating the `libraryTracer`-variable * fix: get the unit test for publisher opentelemetry working again * test: fix the subscriber unit tests for opentelemetry * chore: remove describe.only * chore: latest changes * test: updated the tests * test: improve the tests * chore: maybe its need to be Google LLC? * feat: add messaging attributes to otel spans * fix: include package.json version as instrumentation version * docs: update the opentelemetry example code * style: remove unused code * fix: remove peer name for now * style: improve explanation regarding otel trace provider * chore: update the opentelemetry versios in the samples `package.json` * test: remove extranous logging in the opentelemetry example app * test: remove the check for `traceId` that doesn't get outputted * fix: remove unnecessary messaging span attribute and added comments * style: use shiny new syntax for undefined check in `subscriber`-class * fix: match the span name with the operation kind in `subscriber`-class * chore: improved code based on PR feedback * fix: BREAKING CHANGE: The Opentelemetry tracing span doesn't expose the `data`-attribute anymore to avoid accidentally exposing privacy/personal data * fix: only include `googclient_OpenTelemetrySpanContext`-attribute when valid span context exists * fix: change the way `package.json` is being imported * fix: revert bad merge that removed tracing on devDependencies At least I think that's what happened... * style: remove unnecessary comment * style: remove unused imports * build: downgrade @sinonjs/fake-timers to v6 The v10 of sinonjs comes with v7 of fake-timers which comes with typescript type definitions that are generated by jsdoc comments which seems to cause trouble when compiling the app it. Downgrading to v6 to avoid needing to solve this problem now. * style: cleanup type definition Removed the `| undefined` for the `span` in the `Publisher`-class Co-authored-by: Aaron Abbott <aaronabbott@google.com> * build: remove `package.json` after compilation step * build: put back package.json in the build * build: explicitly add package.json to the npm pack build * fix: revert "fix: change the way `package.json` is being imported" This reverts commit 0c2c76f. * fix: revert "build: explicitly add package.json to the npm pack build" This reverts commit 14de625. Co-authored-by: Weyert de Boer <weyert.deboer@tapico.io> Co-authored-by: Megan Potter <57276408+feywind@users.noreply.github.com> Co-authored-by: Megan Potter <mzp@google.com> Co-authored-by: Aaron Abbott <aaronabbott@google.com>
- Loading branch information