Is there any initiative to add prisma instrumentation to the nodejs layer?

[elnatantorres]

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

I saw that prisma ORM is not included in the packages that the nodejs layer covers.

Describe the solution you'd like

I would like that the open telemetry instrumentation for Prisma was available in nodejs otel layer.

Describe alternatives you've considered

The alternative that I see is adding the prisma instrumentation manually creating a custom layer for the lambdas.

Additional context

--

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[serkan-ozal]

Hi @elnatantorres, I think we should not add 3rd party instrumentation packages to the layer artifact itself. So, I see two options:

• Prisma folks can contribute their instrumentation packages to OpenTelemetry JS contrib repo: https://github.com/open-telemetry/opentelemetry-js-contrib /cc @trentm
• Or you can customize instrumentation list by giving your own configureInstrumentations function. To do that, you can have your init.js and register your custom configureInstrumentations function to the global. Here, your init.js file must be initialized before OTEL, therefore, you need to set NODE_OPTIONS=/var/task/init.js env var. So, your init.js file will be loaded before OTEL Lambda init.mjs (https://github.com/open-telemetry/opentelemetry-lambda/blob/main/nodejs/packages/layer/scripts/otel-handler#L5) and register its custom configureInstrumentations function. Then OTEL layer will use it while adding instrumentations (https://github.com/open-telemetry/opentelemetry-lambda/blob/main/nodejs/packages/layer/src/wrapper.ts#L323).

But, I agree that we should provide easier way to do that.