Summary

We need to update attribute names in the OpenTelemetry spec in compliance with the latest version of the Official OpenTelemetry semantic conventions for database client spans found here: https://opentelemetry.io/docs/specs/semconv/db/database-spans/

The db.system attribute was renamed to db.system.name and we need to reflect that change and update our tests accordingly.

Motivation

Who is the affected end user?

Users of drivers that have already implemented and released OpenTelemetry support

How does this affect the end user?

Users' telemetry data will use non-standard attribute names (db.system instead of db.system.name) that don't match the official OpenTelemetry semantic conventions. This means:
  - Dashboards and monitoring tools expecting standard OTel attribute names won't work correctly
  - Users must write queries/filters using non-standard attribute names
  - Breaks interoperability with OTel-compliant observability platforms and tooling

  This doesn't block users from using the driver, but it breaks compatibility with standard OpenTelemetry tooling and best practices

How likely is it that this problem or use case will occur?

Main path - every user who enables OpenTelemetry tracing in the driver will be affected. This is a guaranteed issue for anyone integrating with OTel-compliant monitoring systems.

If the problem does occur, what are the consequences and how severe are they?

Moderate severity:
  - Telemetry dashboards, queries, and alerting rules expecting standard OTel attribute names won't work
  - Impacts observability and monitoring effectiveness
  - Degrades the value of telemetry data

Is this issue urgent?

Yes - the C# driver OpenTelemetry implementation is currently in PR review and hasn't been released yet. This must be fixed before the first release to avoid introducing a breaking change later. Once released with incorrect attribute names, fixing them would be a breaking change for existing users.

Is this ticket required by a downstream team?

N/A

Is this ticket only for tests?

No - both the driver code and tests need updates

Acceptance Criteria

 1. Attribute names updated in driver code:
    - db.system → db.system.name
    _- All other attribute names verified against latest OTel semantic conventions (https://opentelemetry.io/docs/specs/semconv/db/database-spans/)_
  2. OpenTelemetry spec tests updated:
    - All test assertions updated to expect db.system.name instead of db.system