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 name of the connection pool; unique within the instrumented application. In case the connection pool implementation doesn't provide a name, instrumentation **SHOULD** use a combination of parameters that would make the name unique, for example, combining attributes `server.address`, `server.port`, and `db.namespace`, formatted as `server.address:server.port/db.namespace`. Instrumentations that generate connection pool name following different patterns **SHOULD** document it.
19
25
*
@@ -22,7 +28,7 @@
22
28
* @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
* The name of the database, fully qualified within the serveraddress and port.
44
+
* Deprecated, use `server.address`, `server.port` attributes instead.
38
45
*
39
-
* @example customers
40
-
* @example test.users
41
-
*
42
-
* @note If a database system has multiple namespace components, they **SHOULD** be concatenated (potentially using database system specific conventions) from most general to most specific namespace component, and more specific namespaces **SHOULD NOT** be captured without the more general namespaces, to ensure that "startswith" queries for the more general namespaces will be valid.
43
-
* Semantic conventions for individual database systems **SHOULD** document what `db.namespace` means in the context of that system.
44
-
* It is **RECOMMENDED** to capture the value as provided by the application without attempting to do any case normalization.
45
-
* This attribute has stability level RELEASE CANDIDATE.
* The name of the operation or command being executed.
53
-
*
54
-
* @example findAndModify
55
-
* @example HMSET
56
-
* @example SELECT
55
+
* Deprecated, use `db.namespace` instead.
57
56
*
58
-
* @note It is **RECOMMENDED** to capture the value as provided by the application without attempting to do any case normalization.
59
-
* If the operation name is parsed from the query text, it **SHOULD** be the first operation name found in the query.
60
-
* For batch operations, if the individual operations are known to have the same operation name then that operation name **SHOULD** be used prepended by `BATCH `, otherwise `db.operation.name` **SHOULD** be `BATCH` or some other database system specific term if more applicable.
61
-
* This attribute has stability level RELEASE CANDIDATE.
57
+
* @example customers
58
+
* @example main
62
59
*
63
60
* @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
* If no [tech-specific attribute](#call-level-attributes-for-specific-technologies) is defined, this attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).
111
+
* Deprecated, use `server.port` on client spans and `client.port` on server spans.
116
112
*
117
-
* Note: In some SQL databases, the database name to be used is called "schema name".
113
+
* @example 8080
118
114
*
115
+
* @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
116
+
*
117
+
* @deprecated Replaced by `server.port` on client spans and `client.port` on server spans.
0 commit comments