Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
trask opened this issue Apr 24, 2024 · 5 comments · Fixed by #1101
Closed
Assignees
Labels

Comments

@trask
Copy link
Member

trask commented Apr 24, 2024

Tracking / blocking issue for initial database semconv stability.

@trask
Copy link
Member Author

trask commented Apr 26, 2024

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
Copy link
Member Author

trask commented Apr 26, 2024

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
Copy link
Member Author

trask commented May 8, 2024

  • 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
Copy link
Member Author

trask commented May 8, 2024

what about picking a timeseries database and a vector database?

@gregkalapos
Copy link
Member

gregkalapos commented Jun 28, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

3 participants