You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for the db.namespace attribute mentions "fully qualified within the server address and port." don't think the server address is or should be part of the database name.
Steps to Reproduce (if any)
Expected Result
Actual Result
Semantic convention version
1.27
Additional context
No response
The text was updated successfully, but these errors were encountered:
The documentation for the db.namespace attribute mentions "fully qualified within the server address and port." don't think the server address is or should be part of the database name.
Thank you for reporting this! Could you please elaborate on what's misleading?
The intention is that db.namespace does not contain server.address|port, but uniquely identifies a database that's hosted there.
E.g. I can have mysql running on localhost:3306 and two databases user and orders there.
When connecting to/querying from users, it would result in the following attributes:
Might just be a miss reading from my end. I see it means that it's the fully qualified name of the database within the context of that server and does not mean that it should include the server address and port values directly.
Area(s)
area:db
What happened?
Description
The documentation for the db.namespace attribute mentions "fully qualified within the server address and port." don't think the server address is or should be part of the database name.
Steps to Reproduce (if any)
Expected Result
Actual Result
Semantic convention version
1.27
Additional context
No response
The text was updated successfully, but these errors were encountered: