Does opentelemetry-js fully supports http.server.request.duration?

[JecminekTomas]

Following up to issue in Grafana repository, I'm seeking for help in here.

I've been trying for past week or so to connect metrics with traces in Grafana. But there is an catch, I can't... I've asked Grafana people, if problem is on their side of field and they're redirected me to your community.

Do the opentelemetry-js fully follow http.server.request.duration sementics? I'm not capable of getting seconds metrics at all.

@cijothomas, said back in 23', that seconds are not in specification, but semantics specification explicitly declares units as seconds.
open-telemetry/opentelemetry-dotnet#4165

[maryliag]

Hey @JecminekTomas, I missed your message previously, I replied to the original issue, but adding a reply here too in case other people have the same question.

That metric http.server.request.duration was generated previously with milliseconds, then we added the stable metric that sends in seconds, but currently you need to turn that on.
When we make a change in metrics like this, we need to keep the default for several months, then we can turn that old behaviour off and keep just the latest on by default (The plan for this one is to change the default behaviour in June 2026 so only stable is sent). Since you said you're receiving the metric, just with the wrong unit, I suspect you just need to turn that option on.

To do this, use the OTEL_SEMCONV_STABILITY_OPT_IN environment variable.

• http: emit the new (stable) v1.23.0 semantics
• http/dup: emit both the old v1.7.0 and the new (stable) v1.23.0 semantics
• By default, if OTEL_SEMCONV_STABILITY_OPT_IN includes neither of the above tokens, the old v1.7.0 semconv is used.

You can find this info on the README of the instrumentation-http package here

[JecminekTomas]

Thank you, for your quick response, in this thread :)