[js-contrib] Add dual-emit option for HTTP stable attributes in js-contrib instrumentations

[JamieDanielson]

Issues will be created in js-contrib repo. This is a placeholder for the milestone.

https://opentelemetry.io/docs/specs/semconv/attributes-registry/http/
https://opentelemetry.io/docs/specs/semconv/attributes-registry/network/

instrumentations using http:

• @opentelemetry/instrumentation-nestjs (feat(instrumentation-nestjs-core): support migration to stable HTTP semconv opentelemetry-js-contrib#3080)
  • SEMATTRS_HTTP_METHOD, SEMATTRS_HTTP_URL
• @opentelemetry/instrumentation-aws sdk (feat(instrumentation-aws-sdk): support migration to stable HTTP semconv opentelemetry-js-contrib#3077)
  • SEMATTRS_HTTP_STATUS_CODE
• @opentelemetry/instrumentation-hapi (feat(instrumentation-hapi): support migration to stable HTTP semconv, v1.23.1 opentelemetry-js-contrib#2863)
  • SEMATTRS_HTTP_METHOD and SEMATTRS_HTTP_ROUTE
• @opentelemetry/instrumentation-document-load (feat(instrumentation-document-load): support migration to stable HTTP semconv, v1.23.1 opentelemetry-js-contrib#3075)
  • SEMATTRS_HTTP_URL and SEMATTRS_HTTP_USER_AGENT

instrumentations using net.* (see comment #5663 (comment) below):

• instr-amqplib: support net.* migration as part of stable HTTP semconv migration
• instr-net: feat(instrumentation-net): support net.* semconv migration opentelemetry-js-contrib#3268
• instr-cassandra-driver: support net.* migration as part of stable HTTP semconv migration
• instr-ioredis: feat(instrumentations-ioredis): support net.* and database semconv migration opentelemetry-js-contrib#3266
• instr-knex: feat(instrumentation-knex): Use newer semantic conventions opentelemetry-js-contrib#2671 (See the instr-pg note below. instr-knex also uses OTEL_SEMCONV_STABILITY_OPT_IN=database/dup to handle both db.* and net.* attributes. Likewise, I suggest we keep this as is.)
• instr-memcached: feat(instrumentation-memcached): support net.* and db.* semconv migra… opentelemetry-js-contrib#3169
• instr-mongodb: support net.* migration as part of stable HTTP semconv migration
• instr-mongoose: support net.* migration as part of stable HTTP semconv migration
• instr-mysql: support net.* migration as part of stable HTTP semconv migration
• instr-mysql2: feat(instrumentation-mysql2): support net.* and database semconv migration opentelemetry-js-contrib#3137
• instr-pg: support net.* migration as part of stable HTTP semconv migration. Nope. instr-pg was the first DB-y instrumentation to add support for db.* migration using OTEL_SEMCONV_STABILITY_OPT_IN=database/dup. As part of that change the migration of net.* was handled as well. For backwards compat, I [Trent] am inclined to leave instr-pg as is. I'm happy to change it to use ...OPT_IN=http[/dup] for net.* if we want to prefer consistency, however.
• instr-redis: support net.* migration as part of stable HTTP semconv migration
• feat(instrumentations-tedious): support net.* and database semconv migration opentelemetry-js-contrib#3273

[trentm]

@JamieDanielson,

I think we can remove the following from the list, because the only HTTP-related attribute they use is http.route which is unchanged per the HTTP migration guide:

 @opentelemetry/instrumentation-koa
    SEMATTRS_HTTP_ROUTE

@opentelemetry/instrumentation-router
    SEMATTRS_HTTP_ROUTE

@opentelemetry/instrumentation-restify
    SEMATTRS_HTTP_ROUTE

@opentelemetry/instrumentation-connect
    SEMATTRS_HTTP_ROUTE

@opentelemetry/instrumentation-fastify
    SEMATTRS_HTTP_ROUTE

@opentelemetry/instrumentation-express
    SEMATTRS_HTTP_ROUTE

Doing the simpler update for these packages to use the newer ATTR_ prefix exports can be handled as part of open-telemetry/opentelemetry-js-contrib#2377.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[david-luna]

Comment to avoid auto close