Decide on which `db.system` values to mark stable as part of initial db semconv stability

open-telemetry / semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains

Apache License 2.0

244 stars 158 forks source link

Decide on which `db.system` values to mark stable as part of initial db semconv stability #965

Open trask opened 4 months ago

trask commented 4 months ago

Tracking / blocking issue for initial database semconv stability.

trask commented 4 months ago

Proposal, factoring in the expertise we have within the database working group:

mssql
postgresql
mysql
cosmosdb
elasticsearch

Others that would be nice, based on popularity:

redis
mongodb

trask commented 4 months ago

I suggest we not include hbase in the initial stability, as it will be good to sync with hbase native instrumentation prior to stabilizing anything related to hbase (see #742)

trask commented 3 months ago

sql

there's no db.system constant for sql, should we remove the sql.md page?

but then what to do since there's no oracle, postgresql pages?

==> so keep sql page to document any db.system that implement sql

trask commented 3 months ago

what about picking a timeseries database and a vector database?

gregkalapos commented 2 months ago

WG Meeting: From OTel community day: Redis and Postgres cover a lot - should be marked as stable.