Express spans showing impossible duration_ms

[DAlperin]

What version of OpenTelemetry are you using?

0.33.0

What version of Node are you using?

16 lts

What did you do?

Instrumented node. I use the following to set up my tracing:

import { getNodeAutoInstrumentations } from "@opentelemetry/auto-instrumentations-node";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-proto";
import { NodeSDK } from "@opentelemetry/sdk-node";
import { PrismaInstrumentation } from "@prisma/instrumentation";

const traceExporter = new OTLPTraceExporter();

const sdk = new NodeSDK({
    traceExporter,
    instrumentations: [
        getNodeAutoInstrumentations(),
        new PrismaInstrumentation(),
    ],
});

// eslint-disable-next-line @typescript-eslint/no-floating-promises
sdk.start().then(() => {
    // eslint-disable-next-line no-console
    console.log(`✅ OTLP ready`);
});

What did you expect to see?

Reasonable tracing

What did you see instead?

[rauno56]

@prisma/instrumentation is not hosted here. Have you tried to let them know at https://github.com/prisma/prisma_

[DAlperin]

The issue appears to be in express instrumentation. The issue persists even without the prisma instrumentation enabled.

[vmarchaud]

Could you share the code of the middleware in question ? There can be edge cases that make it hard to track exactly when each middleware is ended

[DAlperin]

Here is where I set up all my middlewares: https://github.com/DAlperin/dov.dev-remix/blob/main/server.ts

[beeme1mr]

I also ran into the same issue. Downgrading to "@opentelemetry/auto-instrumentations-node": "^0.31.2" resolved the issue. It seems like the only noteworthy change for express was requestHook support.

[DAlperin]

@beeme1mr out of curiosity what tool were you using to visualize your traces?

[beeme1mr]

I was using the latest version of Jaeger.

[Flarna]

see also #1209

[dyladan]

#1210