Component(s)

auto-instrumentation

Is your feature request related to a problem? Please describe.

Deno, a modern JavaScript and TypeScript runtime, version 2.1.5 and later, ships with OpenTelemetry support out of the box enabled by setting OTEL_DENO=true. Setting this env var will enable auto-instrumentation of various components of Deno (Deno.serve http server, fetch http client, and more), OTLP exporting for metrics, logs, and traces, and automatic exporting of telemetry created through the JS @opentelemetry/api package from NPM: https://docs.deno.com/runtime/fundamentals/open_telemetry/

Right now it is possible to use OpenTelemetry operator with Deno, by using instrumentation.opentelemetry.io/inject-sdk: "true" and manually setting OTEL_DENO=1 as an env var. This is however not as nice as some other auto-instrumentation, where one just has to set, for example, instrumentation.opentelemetry.io/inject-nginx: "true".

Describe the solution you'd like

Add support for instrumentation.opentelemetry.io/inject-deno: "true", which would be behaviourally equivalent to instrumentation.opentelemetry.io/inject-sdk: "true" and setting OTEL_DENO=true as an env var.

Unlike most (all) other auto-instrumentation, a separate container (image) with auto-instrumentation payload is unneeded, because Deno comes with auto-instrumentation out of the box.

Describe alternatives you've considered

No response

Additional context

Support for OTEL is currently unstable in Deno, and requires that the user pass --unstable-otel when starting to enable. We expect this feature to be stabilized within the next three months.

I will open a PR with the code needed to support this, disabled by default (ie one needs to pass --enable-deno-instrumentation).