From 9fb01e2982417fdb4b12a104024547051813cddf Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Wed, 16 Oct 2024 11:42:38 -0700 Subject: [PATCH] lint --- .chloggen/1482.yaml | 2 +- docs/database/database-spans.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/.chloggen/1482.yaml b/.chloggen/1482.yaml index a327bd7b4d..2f56c01780 100644 --- a/.chloggen/1482.yaml +++ b/.chloggen/1482.yaml @@ -15,4 +15,4 @@ note: | - avoid capturing `db.operation.name` and `db.collection.name` when the query involves multiple operations or collections, to prevent ambiguity. -issues: [521, 805,1159] +issues: [521, 805, 1159] diff --git a/docs/database/database-spans.md b/docs/database/database-spans.md index f52b6caced..8d11a44cdd 100644 --- a/docs/database/database-spans.md +++ b/docs/database/database-spans.md @@ -311,6 +311,7 @@ Instrumentations that support query parsing SHOULD generate query summary when one is not readily available from other sources. The summary SHOULD preserve the following parts of query in the order they were provided: + - operations such as SQL SELECT, INSERT, UPDATE, DELETE or other commands - operation targets such as collection or database names @@ -369,6 +370,7 @@ or other attributes, it SHOULD match the value used in the `db.query.summary`. the corresponding `db.query.summary` is `SELECT songs artists`. - Query that performs an operation on an anonymous table: + ```sql SELECT order_date FROM (SELECT *