It looks like we default to db.name. If we don't find that we try db.system. Do you think this new attribute should take priority over both of these?

So we would look for the following in order and use the first one we found?

• db.system.name
• db.name
• dby.system

db.name was renamed to db.namespace in v1.26.0.

Looking at the current implementation, this ordering would preserve current behavior while supporting the new names:

• db.name
• db.namespace
• db.system
• db.system.name

Blocked by:

• Generate semconv/v1.30.0

@matt-hensley I want to work on this. Can you assign it to me?

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.

I'm bumping this issue as discussed with @cedricziel as OTel practitioners no longer see their databases

As suggested previously, we should make this database name attribute configurable on the service graph processor. That way, if this convention changes yet again, we don't have to worry about making code changes to support the change.

See #4656 (review)

This was done in the otel contrib service graph connector. This config param was recently to support a prioritized list of attribute names for db identification: open-telemetry/opentelemetry-collector-contrib#39133