Add Trino to db.system semantic conventions

open-telemetry · Mar 27, 2023 · 5bbdfd9 · 5bbdfd9
1 parent 0d51a1d
commit 5bbdfd9
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -719,6 +719,8 @@ release.
   ([#2605](https://github.com/open-telemetry/opentelemetry-specification/pull/2605)).
 - Add semantic conventions for hardware metrics
   ([#2518](https://github.com/open-telemetry/opentelemetry-specification/pull/2518)).
+- Add Trino to Database specific conventions
+  ([#3347](https://github.com/open-telemetry/opentelemetry-specification/pull/3347)).
 
 ### Compatibility
 

diff --git a/semantic_conventions/trace/database.yaml b/semantic_conventions/trace/database.yaml
@@ -166,6 +166,9 @@ groups:
             - id: spanner
               value: 'spanner'
               brief: 'Cloud Spanner'
+            - id: trino
+              value: 'trino'
+              brief: 'Trino'
       - id: connection_string
         tag: connection-level
         type: string

diff --git a/specification/trace/semantic_conventions/database.md b/specification/trace/semantic_conventions/database.md
@@ -121,6 +121,7 @@ Some database systems may allow a connection to switch to a different `db.user`,
 | `opensearch` | OpenSearch |
 | `clickhouse` | ClickHouse |
 | `spanner` | Cloud Spanner |
+| `trino` | Trino |
 <!-- endsemconv -->
 
 ### Notes and well-known identifiers for `db.system`