regenerate tables

open-telemetry · Oct 29, 2024 · f4e4c06 · f4e4c06
1 parent a3fd6a6
commit f4e4c06
Show file tree

Hide file tree

Showing 10 changed files with 11 additions and 11 deletions.
diff --git a/docs/database/cassandra.md b/docs/database/cassandra.md
@@ -92,7 +92,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[7]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[7]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[8]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/cosmosdb.md b/docs/database/cosmosdb.md
@@ -341,7 +341,7 @@ Explaining bucket configuration:
 | [`db.namespace`](/docs/attributes-registry/db.md) | string | The name of the database, fully qualified within the server address and port. | `customers`; `test.users` | `Conditionally Required` If available. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`db.operation.name`](/docs/attributes-registry/db.md) | string | The name of the operation or command being executed. [1] | `findAndModify`; `HMSET`; `SELECT` | `Conditionally Required` [2] | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`db.response.status_code`](/docs/attributes-registry/db.md) | string | Database response status code. [3] | `102`; `ORA-17002`; `08P01`; `404` | `Conditionally Required` [4] | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
-| [`db.target.name`](/docs/attributes-registry/db.md) | string | Cosmos DB container name. [5] | `public.users`; `customers` | `Conditionally Required` If available | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`db.target.name`](/docs/attributes-registry/db.md) | string | Cosmos DB container or another entity that the operation is acting upon. [5] | `public.users`; `customers` | `Conditionally Required` If available | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`error.type`](/docs/attributes-registry/error.md) | string | Describes a class of error the operation ended with. [6] | `timeout`; `java.net.UnknownHostException`; `server_certificate_invalid`; `500` | `Conditionally Required` If and only if the operation failed. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
 | [`server.port`](/docs/attributes-registry/server.md) | int | Server port number. [7] | `80`; `8080`; `443` | `Conditionally Required` [8] | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
 | [`server.address`](/docs/attributes-registry/server.md) | string | Name of the database host. [9] | `example.com`; `10.1.2.80`; `/tmp/my.sock` | `Recommended` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |

diff --git a/docs/database/database-metrics.md b/docs/database/database-metrics.md
@@ -149,7 +149,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[8]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[8]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[9]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.
@@ -345,7 +345,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[8]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[8]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[9]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/database-spans.md b/docs/database/database-spans.md
@@ -165,7 +165,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[8]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[8]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[9]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/hbase.md b/docs/database/hbase.md
@@ -24,7 +24,7 @@ The Semantic Conventions for [HBase](https://hbase.apache.org/) extend and overr
 | [`db.namespace`](/docs/attributes-registry/db.md) | string | The HBase namespace. [1] | `mynamespace` | `Conditionally Required` If applicable. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`db.operation.name`](/docs/attributes-registry/db.md) | string | The name of the operation or command being executed. [2] | `findAndModify`; `HMSET`; `SELECT` | `Conditionally Required` If readily available. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`db.response.status_code`](/docs/attributes-registry/db.md) | string | Protocol-specific response code recorded as string. [3] | `200`; `409`; `14` | `Conditionally Required` If response was received. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
-| [`db.target.name`](/docs/attributes-registry/db.md) | string | The HBase table or namespace name. [4] | `mytable`; `ns:table` | `Conditionally Required` If applicable. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`db.target.name`](/docs/attributes-registry/db.md) | string | The HBase table or another entity that the operation is acting upon. [4] | `mytable`; `ns:table` | `Conditionally Required` If applicable. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`error.type`](/docs/attributes-registry/error.md) | string | Describes a class of error the operation ended with. [5] | `timeout`; `java.net.UnknownHostException`; `server_certificate_invalid`; `500` | `Conditionally Required` If and only if the operation failed. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
 | [`server.port`](/docs/attributes-registry/server.md) | int | Server port number. [6] | `80`; `8080`; `443` | `Conditionally Required` [7] | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
 | [`db.operation.batch.size`](/docs/attributes-registry/db.md) | int | The number of queries included in a batch operation. [8] | `2`; `3`; `4` | `Recommended` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |

diff --git a/docs/database/mariadb.md b/docs/database/mariadb.md
@@ -107,7 +107,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[6]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[6]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[7]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/mssql.md b/docs/database/mssql.md
@@ -77,7 +77,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[6]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[6]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[7]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/mysql.md b/docs/database/mysql.md
@@ -107,7 +107,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[6]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[6]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[7]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/postgresql.md b/docs/database/postgresql.md
@@ -114,7 +114,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[6]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[6]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[7]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.

diff --git a/docs/database/sql.md b/docs/database/sql.md
@@ -139,7 +139,7 @@ SHOULD NOT be captured.
 
 This attribute has stability level RELEASE CANDIDATE.
 
-**[6]:** If readily available and if a database call is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
+**[6]:** If readily available and if a database operation is performed on a single target. The target name MAY be parsed from the query text, in which case it SHOULD be the single target name in the query.
 
 **[7]:** The `error.type` SHOULD match the `db.response.status_code` returned by the database or the client library, or the canonical name of exception that occurred.
 When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred.