Database semantic convention stability implementation tracking issue - [x] #11575 - [x] #12601 - [x] ~Use `OTEL_SEMCONV_RC_OPT_IN` instead of `OTEL_SEMCONV_STABILITY_OPT_IN` until database semconv is actually marked stable to avoid confusion(?)~ - [x] #15139 - [x] #15149 - [x] #12802 - [x] #12804 - [x] Rename db getter methods to match stable semconv naming #15696 - [x] Implement the `db.query.summary` attribute (requires updating the jflex sql parsing) #15971 - [x] Improve coverage for jflex sql parsing - [x] #15984 - [x] #15983 - [x] #15979 - [x] #15986 - [x] #16007 - [x] #15980 - [x] #16017 - [x] #15993 - [x] #16077 - [x] #16079 - [x] #16082 - [x] #16085 - [x] #16184 - [x] #16083 - [x] Implement `db.stored_procedure.name` #15836 - [x] Extract `db.stored_procedure.name` from `{call procedure_name()}` (see Hibernate tests) - [x] Handle `EXEC` and `EXECUTE` in addition to `CALL` to identify stored procedures #15971 - [x] Implement `db.operation.batch.size` #12797 - [x] Implement stable span name #15854 - [x] Implement https://github.com/open-telemetry/semantic-conventions/pull/1566 - [x] Implement https://github.com/open-telemetry/semantic-conventions/pull/1560 - [x] Implement https://github.com/open-telemetry/semantic-conventions/pull/1565 - [x] Implement https://github.com/open-telemetry/semantic-conventions/issues/1567 - [x] Implement https://github.com/open-telemetry/semantic-conventions/issues/1491 - [ ] Align `db.namespace` with semconv definitions - [ ] #16080 - [x] Convert connection pool metrics from milliseconds to seconds (https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/12608#issuecomment-2682836593) - [x] Don't sanitize prepared statement text #15855 - [x] Don't capture `db.operation.name`, `db.collection.name` for SQL queries - [x] Terminology renames (statement -> queryText, dbName -> namespace, operation -> operationName) - [x] #16022 - [x] #16023 - [x] #16024 - [x] #16074 - [x] #16133 - [x] #16134 - [x] #16143 - [x] #16144 - [x] #16145 - [x] #16147 - [x] #16150 - [x] #16151 - [ ] Change DbClientAttributesGetter implementations to extend SqlClientAttributesGetter where those modules are leveraging sql sanitization - This can only be done after dropping old semconv since it breaks old semconv span names - [ ] [Share SqlDialect logic between jdbc and vertx sql](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/16254#discussion_r2995896516)
Database semantic convention stability implementation tracking issue
UseOTEL_SEMCONV_RC_OPT_INinstead ofOTEL_SEMCONV_STABILITY_OPT_INuntil database semconv is actually marked stable to avoid confusion(?)db.client.operation.durationmetric #12802error.typeanddb.response.status_codeattributes #12804db.query.summaryattribute (requires updating the jflex sql parsing) Add support fordb.query.summaryin SqlClientAttributesExtractor #15971call next value for sequence#15980db.stored_procedure.nameImplementdb.stored_procedure.namestable semconv attribute #15836db.stored_procedure.namefrom{call procedure_name()}(see Hibernate tests)EXECandEXECUTEin addition toCALLto identify stored procedures Add support fordb.query.summaryin SqlClientAttributesExtractor #15971db.operation.batch.sizeInstrument jdbc batch queries #12797db.operation.nameanddb.collection.namefrom query formats that support multiples semantic-conventions#1566operation.summaryattribute to represent span name semantic-conventions#1567db.namespacewith semconv definitionsdb.namespace#16080db.operation.name,db.collection.namefor SQL queriesstatementSanitizationEnabledtoquerySanitizationEnabled#16143