Azure Monitor OpenTelemetry Exporter does not support current database semantic convention attributes

[jonahmdot]

• azure-monitor-opentelemetry: 1.8.9
• Operating System: Ubuntu
• Python Version: 3.14

Describe the bug

The Azure Monitor OpenTelemetry Exporter does not recognize the current OpenTelemetry database semantic convention attributes when converting CLIENT spans to Application Insights dependencies.

For example, a Redis span using:

db.system.name = redis
db.operation.name = GET
db.query.text = GET ?

is exported with DependencyType = N/A.

Adding the deprecated attributes:

db.system = redis
db.operation = GET
db.statement = GET ?

causes the same span to be correctly exported with DependencyType = redis.

To Reproduce

1. Create an OpenTelemetry CLIENT span with:

   • db.system.name = redis
   • db.operation.name = GET
   • optionally db.query.text = GET ?

2. Export it using azure-monitor-opentelemetry.

3. Check the resulting AppDependencies telemetry in Application Insights.

4. Observe that the dependency type is N/A.

5. Add the deprecated db.system = redis attribute and repeat.

6. Observe that the dependency type is now redis.

Expected behavior

The exporter should support the current database semantic convention attributes such as db.system.name, db.operation.name, and db.query.text without requiring the deprecated db.system, db.operation, and db.statement attributes.

Additional context

The exporter currently appears to rely on the deprecated database semantic convention attributes when mapping database spans to Application Insights dependencies.

Related: #34246

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc Hector Hernandez (@hectorhdzg) Jackson Weber (@JacksonWeber) Jeremy Voss (@jeremydvoss) Leighton Chen (@lzchen) Nev (@MSNev) Radhika Gupta (@rads-1996).