Stable HTTP Semconv Instrumentation Status

[trask]

@open-telemetry/browser-maintainers @open-telemetry/cpp-approvers @open-telemetry/cpp-contrib-approvers @open-telemetry/dotnet-contrib-approvers @open-telemetry/erlang-approvers @open-telemetry/erlang-contrib-approvers @open-telemetry/go-approvers @open-telemetry/java-instrumentation-approvers @open-telemetry/javascript-approvers @open-telemetry/opentelemetry-python-contrib-approvers @open-telemetry/php-approvers @open-telemetry/ruby-contrib-approvers @open-telemetry/rust-approvers @open-telemetry/swift-approvers

Can you please validate the data I scraped via AI below? For cases where stable HTTP semconv is supported but old HTTP semconv is still emitted by default (🔄), can you share any plans you have for making the switch to emitting stable HTTP semconv by default? Thanks!

---

.NET

Package	Type	Semconv Status
OpenTelemetry.Instrumentation.AspNet	Server	✅ Stable
OpenTelemetry.Instrumentation.AspNetCore	Server	✅ Stable
OpenTelemetry.Instrumentation.GrpcNetClient	Client	✅ Stable
OpenTelemetry.Instrumentation.Http	Client	✅ Stable
OpenTelemetry.Instrumentation.Owin	Server	✅ Stable

C++

Package	Type	Semconv Status
httpd	Server	✅ Stable
nginx	Server	✅ Stable
otel-webserver-module	Server	❌ Old

Erlang/Elixir

Package	Type	Semconv Status
opentelemetry_bandit	Server	✅ Stable
opentelemetry_cowboy	Server	✅ Stable
opentelemetry_elli	Server	❌ Old
opentelemetry_finch	Client	❌ Old
opentelemetry_httpoison	Client	❌ Old
opentelemetry_phoenix	Server	✅ Stable
opentelemetry_req	Client	✅ Stable
opentelemetry_tesla	Client	✅ Stable

Go

Package	Type	Semconv Status
otelecho	Server	✅ Stable
otelgin	Server	✅ Stable
otelhttp	Client/Server	✅ Stable
otelhttptrace	Client	✅ Stable
otelmux	Server	✅ Stable
otelrestful	Server	✅ Stable

Java

Package	Type	Semconv Status
akka-http	Client/Server	✅ Stable
apache-httpasyncclient	Client	✅ Stable
apache-httpclient	Client	✅ Stable
armeria	Client/Server	✅ Stable
async-http-client	Client	✅ Stable
grizzly	Server	✅ Stable
helidon	Server	✅ Stable
http-url-connection	Client	✅ Stable
java-http-client	Client	✅ Stable
java-http-server	Server	✅ Stable
jax-rs	Server	✅ Stable
jetty-httpclient	Client	✅ Stable
jodd-http	Client	✅ Stable
netty	Client/Server	✅ Stable
okhttp	Client	✅ Stable
pekko-http	Client/Server	✅ Stable
ratpack	Client/Server	✅ Stable
reactor-netty	Client	✅ Stable
restlet	Server	✅ Stable
servlet	Server	✅ Stable
spring-webflux	Client/Server	✅ Stable
spring-webmvc	Server	✅ Stable
tomcat	Server	✅ Stable
undertow	Server	✅ Stable
vertx-http-client	Client	✅ Stable
vertx-web	Server	✅ Stable

JavaScript (Browser)

Package	Type	Semconv Status
instrumentation-document-load	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-fetch	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-xml-http-request	Client	🔄 Old - http, http/dup available

JavaScript (Node.js)

Package	Type	Semconv Status
instrumentation-undici	Client	✅ Stable
instrumentation-http	Client/Server	🔄 Old - http, http/dup available
instrumentation-aws-sdk	Client	🔄 Old - http, http/dup available
instrumentation-hapi	Server	🔄 Old - http, http/dup available
instrumentation-nestjs-core	Server	🔄 Old - http, http/dup available

Then a number of instrumentations that use OTEL_SEMCONV_STABILITY_OPT_IN=http[/dup]
only for net.* attributes that were migrated in
the HTTP migration doc.

Package	Type	Semconv Status
instrumentation-grpc	Low-level	🔄 Old - http, http/dup available
instrumentation-cassandra-driver	Low-level	🔄 Old - http, http/dup available
instrumentation-ioredis	Low-level	🔄 Old - http, http/dup available
instrumentation-memcached	Low-level	🔄 Old - http, http/dup available
instrumentation-mongodb	Low-level	🔄 Old - http, http/dup available
instrumentation-amqplib	Low-level	🔄 Old - http, http/dup available
instrumentation-net	Low-level	🔄 Old - http, http/dup available
instrumentation-mysql2	Low-level	🔄 Old - http, http/dup available
instrumentation-tedious	Low-level	🔄 Old - http, http/dup available
instrumentation-mongoose	Low-level	🔄 Old - http, http/dup available
instrumentation-mysql	Low-level	🔄 Old - http, http/dup available

PHP

Package	Type	Semconv Status
CakePHP	Server	✅ Stable
CodeIgniter	Server	✅ Stable
Curl	Client	✅ Stable
Guzzle	Client	✅ Stable
Laravel	Server	✅ Stable
Psr15	Server	✅ Stable
Psr18	Client	✅ Stable
ReactPHP	Client	✅ Stable
Slim	Server	✅ Stable
Symfony	Server	✅ Stable
Symfony/HttpClient	Client	✅ Stable
WordPress	Server	✅ Stable
Yii	Server	✅ Stable

Python

Package	Type	Semconv Status
opentelemetry-instrumentation-aiohttp-client	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-aiohttp-server	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-asgi	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-django	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-falcon	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-fastapi	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-flask	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-httpx	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-pyramid	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-requests	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-starlette	Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-tornado	Client/Server	🔄 Old - http, http/dup available
opentelemetry-instrumentation-urllib	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-urllib3	Client	🔄 Old - http, http/dup available
opentelemetry-instrumentation-wsgi	Server	🔄 Old - http, http/dup available

Ruby

Package	Type	Semconv Status
ethon	Client	🔄 Old - http, http/dup available
excon	Client	🔄 Old - http, http/dup available
faraday	Client	🔄 Old - http, http/dup available
http	Client	🔄 Old - http, http/dup available
http_client	Client	🔄 Old - http, http/dup available
httpx	Client	🔄 Old - http, http/dup available
net_http	Client	🔄 Old - http, http/dup available
rack	Server	🔄 Old - http, http/dup available
rails	Server	🔄 Old - http, http/dup available
restclient	Client	🔄 Old - http, http/dup available
sinatra	Server	🔄 Old - http, http/dup available

Rust

Package	Type	Semconv Status
opentelemetry-instrumentation-actix-web	Client/Server	✅ Stable
opentelemetry-instrumentation-tower	Server	✅ Stable

Swift

Package	Type	Semconv Status
URLSession	Client	🔄 Old - .old, .stable, .httpDup available

[yordis]

Working on Elixir side, @tsloughter ^

[martincostello]

For .NET the instrumentations listed are all stable, but support http/dup has been removed.

[dmathieu]

The same applied to the Go instrumentations. We are using the stable semantic conventions, and http/dup has been removed.

[hannahramadan]

For Ruby, we are planning to emit stable conventions by default and remove http/dup at the end of February/early March.

[trentm]

For JavaScript:

1. The browser section is correct.
2. Here is a replacement for the JavaScript (Node.js) section:

## JavaScript (Node.js)

| Package | Type | Semconv Status |
| ------- | ---- | -------------- |
| instrumentation-undici      | Client        | ✅ Stable |
| instrumentation-http        | Client/Server | 🔄 Old - http, http/dup available |
| instrumentation-aws-sdk     | Client        | 🔄 Old - http, http/dup available |
| instrumentation-hapi        | Server        | 🔄 Old - http, http/dup available |
| instrumentation-nestjs-core | Server        | 🔄 Old - http, http/dup available |

Then a number of instrumentations that use `OTEL_SEMCONV_STABILITY_OPT_IN=http[/dup]`
only for `net.*` attributes that were migrated in 
[the HTTP migration doc](https://opentelemetry.io/docs/specs/semconv/non-normative/http-migration/).

| Package | Type | Semconv Status |
| ------- | ---- | -------------- |
| instrumentation-grpc              | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-cassandra-driver  | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-ioredis           | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-memcached         | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-mongodb           | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-amqplib           | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-net               | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-mysql2            | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-tedious           | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-mongoose          | Low-level | 🔄 Old - http, http/dup available |
| instrumentation-mysql             | Low-level | 🔄 Old - http, http/dup available |

3. Our plan is to have a JS SDK v3 release in ~6 months -- around June to coincide with Node.js core dropping support for v20. That "v3" release will change to stable HTTP and DB semconv by default. This is documented here: https://github.com/open-telemetry/opentelemetry-js/blob/main/doc/semconv-stable-http-and-database.md though that hasn't really be shared widely. I used this as a reminder to finally update the status of that doc now that all JS instrumentations support the OPT_IN envvar for http and db.