opentelemetry-js icon indicating copy to clipboard operation
opentelemetry-js copied to clipboard

OpenTelemetry JavaScript Client

Results 635 opentelemetry-js issues
Sort by recently updated
recently updated
newest added
trafficstars

# Which problem is this PR solving? The penguins are losing homes Please include a summary of the change and which issue is fixed. Please also include relevant motivation and...

stale

- [x] This may affect other libraries, but I would like to get opinions here first ## Setup Node JS Lambda using the OpenTelemetry Lambda SDK and Collector Layers, with...

stale

## Which problem is this PR solving? This PR introduces a conditional unref feature to the Prometheus Exporter within the OpenTelemetry JavaScript project. Previously, the unref method was called unconditionally,...

## Which problem is this PR solving? The `AsyncHooksContextManager` currently depends on the Node.js specific API `async_hooks` in order to make use of `AsyncLocalStorage`. Other JS runtimes, like for example...

## Which problem is this PR solving? I'm running this exporter in a worker thread (using a pino logger), and since in that context process.stdout is not a TTY, the...

As it says on the tin. I've had this kicking around for a while but never got to actually open the PR.

dependencies
Skip Changelog

## Which problem is this PR solving? Fixes #4552 #4451 ## Short description of the changes See #4552. I hope changes to `LoggerProviderConfig` are not breaking. It is exported but...

# Background ### Discussed in https://github.com/open-telemetry/opentelemetry-js/discussions/4807 Originally posted by **yaohongkok** June 18, 2024 I have a Collector running on `b.example.com`. CORS is enabled on my Collector, and a custom authenticator...

We should bump `typescript` to latest in the next major version. As a part of this PR we should document the following: - Document policy that typescript versions will be...

never-stale
triage:accepted

### Is your feature request related to a problem? Please describe. Currently when a `MeterProvider` is registered via `metrics.setMeterProvider()` after acquiring a `metrics.getMeterProivder()` elsewhere, the previously acquired `MeterProvider` will stay...

feature-request
never-stale
api:metrics