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
Copy file name to clipboardExpand all lines: opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/az_attributes.py
+5
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,11 @@
14
14
15
15
fromtypingimportFinal
16
16
17
+
AZ_NAMESPACE: Final="az.namespace"
18
+
"""
19
+
[Azure Resource Provider Namespace](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-services-resource-providers) as recognized by the client.
A guid describing the concrete instance of the event source.
111
+
Note: CloudFoundry defines the `instance_id` in the [Loggregator v2 envelope](https://github.com/cloudfoundry/loggregator-api#v2-envelope).
112
+
It is used for logs and metrics emitted by CloudFoundry. It is
113
+
supposed to contain the vm id for CloudFoundry components.
114
+
115
+
When system components are instrumented, values from the
Copy file name to clipboardExpand all lines: opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/container_attributes.py
The unique volume ID returned by the CSI ([Container Storage Interface](https://github.com/container-storage-interface/spec)) plugin.
50
+
Note: This can sometimes be referred to as a "volume handle" in CSI implementations. This should represent the `Volume.volume_id` field in CSI spec.
51
+
"""
52
+
41
53
CONTAINER_ID: Final="container.id"
42
54
"""
43
-
Container ID. Usually a UUID, as for example used to [identify Docker containers](https://docs.docker.com/engine/reference/run/#container-identification). The UUID might be abbreviated.
55
+
Container ID. Usually a UUID, as for example used to [identify Docker containers](https://docs.docker.com/engine/containers/run/#container-identification). The UUID might be abbreviated.
Copy file name to clipboardExpand all lines: opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/db_attributes.py
+47-32
Original file line number
Diff line number
Diff line change
@@ -80,11 +80,12 @@
80
80
Note: It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
81
81
If the collection name is parsed from the query text, it SHOULD be the first collection name found in the query and it SHOULD match the value provided in the query text including any schema and database name prefix.
82
82
For batch operations, if the individual operations are known to have the same collection name then that collection name SHOULD be used, otherwise `db.collection.name` SHOULD NOT be captured.
83
+
This attribute has stability level RELEASE CANDIDATE.
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.
177
178
Semantic conventions for individual database systems SHOULD document what `db.namespace` means in the context of that system.
178
179
It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
180
+
This attribute has stability level RELEASE CANDIDATE.
The number of queries included in a [batch operation](/docs/database/database-spans.md#batch-operations).
190
+
The number of queries included in a batch operation.
189
191
Note: Operations are only considered batches when they contain two or more operations, and so `db.operation.batch.size` SHOULD never be `1`.
192
+
This attribute has stability level RELEASE CANDIDATE.
190
193
"""
191
194
192
195
DB_OPERATION_NAME: Final="db.operation.name"
@@ -195,13 +198,15 @@
195
198
Note: It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
196
199
If the operation name is parsed from the query text, it SHOULD be the first operation name found in the query.
197
200
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.
201
+
This attribute has stability level RELEASE CANDIDATE.
A query parameter used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being a string representation of the parameter value.
203
207
Note: Query parameters should only be captured when `db.query.text` is parameterized with placeholders.
204
208
If a parameter has no name and instead is referenced only by index, then `<key>` SHOULD be the 0-based index.
209
+
This attribute has stability level RELEASE CANDIDATE.
205
210
"""
206
211
207
212
DB_QUERY_TEXT: Final="db.query.text"
@@ -210,13 +215,22 @@
210
215
Note: For sanitization see [Sanitization of `db.query.text`](../../docs/database/database-spans.md#sanitization-of-dbquerytext).
211
216
For batch operations, if the individual operations are known to have the same query text then that query text SHOULD be used, otherwise all of the individual query texts SHOULD be concatenated with separator `; ` or some other database system specific separator if more applicable.
212
217
Even though parameterized query text can potentially have sensitive data, by using a parameterized query the user is giving a strong signal that any sensitive data will be passed as parameter values, and the benefit to observability of capturing the static part of the query text by default outweighs the risk.
218
+
This attribute has stability level RELEASE CANDIDATE.
Note: The status code returned by the database. Usually it represents an error code, but may also represent partial success, warning, or differentiate between various types of successful outcomes.
230
+
Semantic conventions for individual database systems SHOULD document what `db.response.status_code` means in the context of that system.
231
+
This attribute has stability level RELEASE CANDIDATE.
232
+
"""
233
+
220
234
DB_SQL_TABLE: Final="db.sql.table"
221
235
"""
222
236
Deprecated: Replaced by `db.collection.name`.
@@ -231,6 +245,7 @@
231
245
"""
232
246
The database management system (DBMS) product as identified by the client instrumentation.
233
247
Note: The actual DBMS may differ from the one identified by the client. For example, when using PostgreSQL client libraries to connect to a CockroachDB, the `db.system` is set to `postgresql` based on the instrumentation's best knowledge.
248
+
This attribute has stability level RELEASE CANDIDATE.
234
249
"""
235
250
236
251
DB_USER: Final="db.user"
@@ -287,36 +302,36 @@ class DbCosmosdbConnectionModeValues(Enum):
287
302
288
303
289
304
classDbCosmosdbOperationTypeValues(Enum):
290
-
INVALID="Invalid"
291
-
"""invalid."""
292
-
CREATE="Create"
305
+
BATCH="batch"
306
+
"""batch."""
307
+
CREATE="create"
293
308
"""create."""
294
-
PATCH="Patch"
295
-
"""patch."""
296
-
READ="Read"
297
-
"""read."""
298
-
READ_FEED="ReadFeed"
299
-
"""read_feed."""
300
-
DELETE="Delete"
309
+
DELETE="delete"
301
310
"""delete."""
302
-
REPLACE="Replace"
303
-
"""replace."""
304
-
EXECUTE="Execute"
311
+
EXECUTE="execute"
305
312
"""execute."""
306
-
QUERY="Query"
307
-
"""query."""
308
-
HEAD="Head"
313
+
EXECUTE_JAVASCRIPT="execute_javascript"
314
+
"""execute_javascript."""
315
+
INVALID="invalid"
316
+
"""invalid."""
317
+
HEAD="head"
309
318
"""head."""
310
-
HEAD_FEED="HeadFeed"
319
+
HEAD_FEED="head_feed"
311
320
"""head_feed."""
312
-
UPSERT="Upsert"
313
-
"""upsert."""
314
-
BATCH="Batch"
315
-
"""batch."""
316
-
QUERY_PLAN="QueryPlan"
321
+
PATCH="patch"
322
+
"""patch."""
323
+
QUERY="query"
324
+
"""query."""
325
+
QUERY_PLAN="query_plan"
317
326
"""query_plan."""
318
-
EXECUTE_JAVASCRIPT="ExecuteJavaScript"
319
-
"""execute_javascript."""
327
+
READ="read"
328
+
"""read."""
329
+
READ_FEED="read_feed"
330
+
"""read_feed."""
331
+
REPLACE="replace"
332
+
"""replace."""
333
+
UPSERT="upsert"
334
+
"""upsert."""
320
335
321
336
322
337
classDbSystemValues(Enum):
@@ -383,19 +398,19 @@ class DbSystemValues(Enum):
383
398
INTERBASE="interbase"
384
399
"""InterBase."""
385
400
MARIADB="mariadb"
386
-
"""MariaDB."""
401
+
"""MariaDB (This value has stability level RELEASE CANDIDATE)."""
387
402
MAXDB="maxdb"
388
403
"""SAP MaxDB."""
389
404
MEMCACHED="memcached"
390
405
"""Memcached."""
391
406
MONGODB="mongodb"
392
407
"""MongoDB."""
393
408
MSSQL="mssql"
394
-
"""Microsoft SQL Server."""
409
+
"""Microsoft SQL Server (This value has stability level RELEASE CANDIDATE)."""
395
410
MSSQLCOMPACT="mssqlcompact"
396
411
"""Deprecated: Removed, use `other_sql` instead."""
397
412
MYSQL="mysql"
398
-
"""MySQL."""
413
+
"""MySQL (This value has stability level RELEASE CANDIDATE)."""
399
414
NEO4J="neo4j"
400
415
"""Neo4j."""
401
416
NETEZZA="netezza"
@@ -409,7 +424,7 @@ class DbSystemValues(Enum):
409
424
POINTBASE="pointbase"
410
425
"""PointBase."""
411
426
POSTGRESQL="postgresql"
412
-
"""PostgreSQL."""
427
+
"""PostgreSQL (This value has stability level RELEASE CANDIDATE)."""
0 commit comments