opentelemetry-js
opentelemetry-js copied to clipboard
OpenTelemetry JavaScript Client
**NB:** Before opening a feature request against this repo, consider whether the feature should/could be implemented in the [other OpenTelemetry client libraries](https://github.com/open-telemetry/). If so, please [open an issue on opentelemetry-specification](https://github.com/open-telemetry/opentelemetry-specification/issues/new)...
Currently, we don't auto-configure a `MetricReader`/exporter combination when using the `@opentelemetry/sdk-node` package. Goal of this issue is to implement exporter selection for metrics based on this specification: - https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#exporter-selection **For...
### What happened? ## Steps to Reproduce 1. Setup application with fetch instrumentation 2. Add a POST call (type of call shouldn't matter, but that's what ours was) 3. Add...
The `@opentelemetry/instrumentation` package exports a `InstrumentationOption` type: ```ts export type InstrumentationOption = | typeof InstrumentationBase | (typeof InstrumentationBase)[] | Instrumentation | Instrumentation[]; ``` However, `InstrumentationBase` implements `Instrumentation` already. Further, this...
This fixes two issues in `registerGlobal` handling in the API. ## make failed diag.setLogger not be silent First, in the following script the second `diag.setLogger` fails to register, because API...
## Which problem is this PR solving? This is based on @clintonb's work on adding a `createGauge()` API. We did not have a way to introduce experimental API features for...
## 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...
### Is your feature request related to a problem? Please describe. Per spec [here](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#instrumentation-scope), InstrumentationScope may hold additional attributes. The proto definition includes the [attributes](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/common/v1/common.proto#L75) field.
## Which problem is this PR solving? Updates https://github.com/open-telemetry/opentelemetry-js/issues/4567 ## Short description of the changes Replace SemanticAttributes.* with specific exported strings for xml-http-request instrumentation package. ## Type of change Please...
### Discussed in https://github.com/open-telemetry/opentelemetry-js/discussions/4313 Originally posted by **jurabek** November 21, 2023 The current version of `opentelemetry-instrumentation-http` has a limitation [where it removes attributes](https://github.com/open-telemetry/opentelemetry-js/blob/079c1f547a32b84e775f1df850b8e66f575ed7ca/experimental/packages/opentelemetry-instrumentation-http/src/utils.ts#L376) from `outgoing-request` and `incoming-request` metrics due to...