opentelemetry-js

opentelemetry-js copied to clipboard

## Description The [OpenTelemetry OTLP exporter spec REQUIRES us to implement a `compression` option for browser exporters](https://github.com/open-telemetry/opentelemetry-specification/blob/9eee5293f95b9fd74f6f1c280b97f87aaec872d7/specification/protocol/exporter.md?plain=1#L13-L14): > The following configuration options MUST be available to configure the OTLP exporter....

pichlermarc

Add option to dual-emit HTTP attributes and finish HTTP migration

7

## Background Issue #4572 is the Semantic Convention Update: Tracking Issue for the migration to stable HTTP attributes. There is a migration plan that includes providing the option to dual-emit...

JamieDanielson

[instrumentation-grpc] emit metrics according to semantic conventions

1

## Description > [!NOTE] > This issue is in refinement stage, requirements and blockers are subject to change > [!WARNING] > **The three issues linked below (#4897, semconv updates) are...

pichlermarc

I think the current `headersToSpanAttributes` may be getting things wrong. Using this example instrumentation and HTTP-using script: https://gist.github.com/trentm/ce3568c01d1328d0769f136c3d24d6bb which configures the instrumentation with: ``` new HttpInstrumentation({ headersToSpanAttributes: { client: {...

trentm

do instr-fetch and instr-xhr *need* to provide configurability of "HTTP known methods" for `http.request.method`?

3

Good point. It'll "work" but get `undefined` everytime, because it'll get this implementation: https://github.com/open-telemetry/opentelemetry-js/blob/v2.0.0/packages/opentelemetry-core/src/platform/browser/environment.ts#L29-L31 So this should probably change. BTW, the same code exists in instrumentation-fetch currently. The spec [says](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-spans.md#http-client-span):...

trentm

PeriodicExportingMetricReader: timeout can be greater than interval

1

### What happened? A `PeriodicExportingMetricReader` has a `_exportInterval` and a `_exportTimeout`, that can optionally be specified via `options` in the constructor. If not specified, they will default to 60s and...

sburuiana-snyk

@opentelemetry/exporter-trace-otlp-grpc ignores headers

3

Hello! According to the [documentation](https://opentelemetry.io/docs/languages/js/exporters/#usage-with-nodejs), it is possible to provide custom headers when configuring the OTLP trace exporter: ```js new OTLPTraceExporter({ // optional - default url is http://localhost:4318/v1/traces url: '/v1/traces',...

ruslan-mikhailov

Default exporter that supports OTLP/HTTP via HTTP/2

1

### Is your feature request related to a problem? Please describe. [There's currently no exporter that supports OTLP/HTTP via HTTP/2 ](https://github.com/open-telemetry/opentelemetry-js/issues/5615#issuecomment-2804669595) ### Describe the solution you'd like As discussed earlier...

I576510

refactor(context-async-hooks): fix eslint warnings

2

## Which problem is this PR solving? Fix the following eslint warnings in the opentelemetry-context-async-hooks package: ``` /home/runner/work/opentelemetry-js/opentelemetry-js/packages/opentelemetry-context-async-hooks/src/AbstractAsyncHooksContextManager.ts 72:35 warning Don't use `Function` as a type @typescript-eslint/ban-types 134:60 warning Don't...

chancancode

refactor(instrumentation-http): fix eslint warnings

2

## Which problem is this PR solving? Fixes the following eslint warnings: ``` /home/runner/work/opentelemetry-js/opentelemetry-js/experimental/packages/opentelemetry-instrumentation-http/src/http.ts 236:41 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any 251:31 warning Unexpected any. Specify a different...

chancancode