Skip to content

Better guidance on semantic conventions for database client call span names in case of missing information #704

@Brar

Description

@Brar

What are you trying to achieve?
When tracing an activity from Npgsql (.NET Database provider for PostgreSQL) we want to set a valid span name according to the semantic conventions for database client calls without having to parse the database statement on the client side and without having to guess (or rather infer from our knowledge on the current default behavior of PostgreSQL) information that we don't have when issuing a database client call.

What did you expect to see?
Guidance on creating a valid span name in cases where all three of db.operation, db.name and db.sql.table are not available to the database client.
Per discussion following npgsql/npgsql#4757 (comment) we think that it is probably pretty safe to infer the database name from our knowledge on PostgreSQL's default behavior but we may still want to research/discuss what good alternatives could be.

Additional context.
https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/database/
npgsql/npgsql#4757 (comment)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions