opentelemetry-js
opentelemetry-js copied to clipboard
open-telemetry
OpenTelemetry JavaScript Client
[](https://renovatebot.com) This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use...
## Description The `@opentelemetry/instrumenation` package is the base package used for all instrumentations. To reduce the maintenance burden for instrumentation authors which currently need to deal with possible breaking changes...
### Description: Types from `@opentelemetry/api-logs` are used in the public interface and may break compatibility when using different versions of the instrumentation base in the same app. It also may...
#### Description: `@types/shimmer` is currently [part of the `@opentelemetry/instrumentation` package's public API](https://github.com/open-telemetry/opentelemetry-js/blob/01a2c35a694e57df45f063d61506ef9e9938eb7d/experimental/packages/opentelemetry-instrumentation/src/instrumentation.ts#L73-L80). We should avoid having a third-party dependency be part of the public API of this package as breaking...
## Which problem is this PR solving? Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that...
Today, some packages define a peer dependency on `@opentelemetry/api` that explicitly excludes future versions in the 1.x range. IMHO this is not helpful because 1.x release have to be backwards...
### What happened? ## Steps to Reproduce Install latest updates ## Expected Result Types to pass ## Actual Result Type error: (see below) ### OpenTelemetry Setup Code Code ```JavaScript import...
I have a Next.js application, and I'd like to send OpenTelemetry logs to Azure Application Insights. Can you provide an example, and are there any links you can share? Additionally,...
## Which problem is this PR solving? Fix #4712, related to #3713. TypeScript emits `InstrumentationNodeModuleDefinition` with ` | undefined` for some reason, making it incompatible with `InstrumentationModuleDefinition` under `exactOptionalPropertyTypes: true`....
I have a basic NextJS application, inside which there are some custom build scripts which run as prebuild alongside the default `next build` package.json: ``` "scripts": { "dev": "next dev",...
