opentelemetry-js
opentelemetry-js copied to clipboard
open-telemetry
OpenTelemetry JavaScript Client
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/typescript-eslint) ([source](https://togithub.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin)) | [`5.59.11` -> `7.1.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/5.59.11/7.1.0) |...
OTELJS uses `@opentelemetry/api/build/src/internal/global-utils.js`, which provides value for managing the singleton nature of tracing resources. Use of globals makes sense in prod at runtime, but during tests, if you bring servers...
## API 1.8.0 ### :rocket: (Enhancement) * feat(api): add SugaredTracer for functions not defined in the spec [#3317](https://github.com/open-telemetry/opentelemetry-js/pull/3317) @secustor ### :bug: (Bug Fix) * fix(api): fix unreachable @opentelemetry/api/experimental entry [#4446](https://github.com/open-telemetry/opentelemetry-js/pull/4446)...
Now that we've removed support for old runtimes, we can use the new diagnostics channels to instrument node core http libraries. ## Known issues ### `http.client.request.start` - `event.request` is not...
## Which problem is this PR solving? It upgrades to the latest version of Typescript. Fixes #3955 ## Short description of the changes Upgrades Typescript and Typedoc (as the version...
### Is your feature request related to a problem? Please describe. Currently, we have to implement these metrics via middleware. But I assume they should be coming from instrumentation packages....
Also consider remove `AsyncHooksContextManager` because it will no longer be used. _Originally posted by @dyladan in https://github.com/open-telemetry/opentelemetry-js/issues/3720#issuecomment-1823194259_ No longer used in SDK 2.0 so it can be safely removed.
## Background Our current internal format for exportable telemetry like spans and metrics (and maybe events) does not match the format expected by the `protobuf` serialization library we are using....
We are running into max metric batch exporting size. ``` PeriodicExportingMetricReader: metrics export failed (error Error: 8 RESOURCE_EXHAUSTED: grpc: received message larger than max (8081061 vs. 4194304))\n at doExport (/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:75:23)...
…nd transfer size ## Which problem is this PR solving? I'm working on a project to collect telemetry about the network utilization of a frontend application. This PR adds two...
