open-telemetry/opentelemetry-dotnet-contrib Instrumentation.EntityFrameworkCore-1.20.2-beta.1

on GitHub

NuGet: OpenTelemetry.Instrumentation.EntityFrameworkCore v1.20.2-beta.1

• Fixed db.query.summary so that a delimited identifier, such as [Orders] or
  [dbo].[Orders], is captured wherever an undelimited identifier would be
  (for example after INSERT INTO, EXEC, CREATE TABLE or a JOIN which
  follows an ON clause), instead of only in a FROM clause.
  (#5816)

• Fixed suppressed or unsampled nested commands enriching or stopping an outer
  command's activity.
  (#5821)

• Fixed a bracketed identifier which contains quotes and a comment marker, such
  as [Orders''--], being parsed as SQL, which truncated the sanitized query
  text and left a literal after it unsanitized if it was on a later line.
  (#5827)

• Fixed the time taken to sanitize a statement when it contains many IN ( lists
  which are not terminated.
  (#5827)

• Fixed literals in a list of values in brackets (e.g. ['a', 'b']) being left
  unsanitized if the list starts with a string in dollar quotes, a string with a
  prefix, a number or a comment, or has a comment which contains a closing
  bracket.
  (#5827)

• Updated the Semantic Conventions version used for the database semantic
  conventions emitted when OTEL_SEMCONV_STABILITY_OPT_IN includes database
  or database/dup to 1.45.0.
  (#5833)

• Fixed db.query.summary so that a multi-part name which mixes undelimited
  and delimited parts, such as dbo.[Orders], or which has whitespace around
  a period, such as dbo . Orders or [dbo] . [Orders], is captured whole,
  and so that a trailing period is no longer left in the summary when no
  further part of the name follows it. As the summary is used to name the
  span, the names of affected spans change.
  (#5822)

• Fixed db.query.summary so that the table name is included for a
  TRUNCATE statement, with or without TABLE, for example
  TRUNCATE TABLE Orders rather than TRUNCATE TABLE.
  (#5822)

• Fixed the cache of sanitized SQL statements retaining statements of any
  length for the lifetime of the process. Statements longer than 8192
  characters are no longer cached.
  (#5869)

• Fixed provider-specific query sanitization for Cloud Spanner (GoogleSQL)
  literals, comments and escaped backtick identifiers, Firebird q'...'
  literals using whitespace or apostrophe delimiters, SQL Server and SQLite
  bracketed identifiers, and databases whose block comments do not nest.
  (#5905)

• Fixed redaction of login and user names in additional CREATE, ALTER and
  DROP statement positions, MySQL account lists and RENAME USER
  statements, including additional Unicode account-name forms and PostgreSQL
  Unicode-escaped identifiers and their UESCAPE clauses.
  (#5905)

• Fixed redaction of Oracle passwords in IDENTIFIED BY and REPLACE
  clauses, including unquoted and double-quoted values and non-ASCII
  characters, and Teradata PASSWORD = values.
  (#5905)

• Fixed db.query.summary for identifiers beginning with SQL keywords and
  login or user statements in multi-statement commands.
  (#5905)

• Fixed PostgreSQL query sanitization for dollar signs in identifiers,
  including combining marks and supplementary characters before digits,
  and dollar-quoted literals with non-ASCII tags.
  (#5905)

• Fixed query sanitization so that dollar-prefixed identifiers and parameters
  in MySQL, SQL Server and SQLite, and Oracle conditional compilation
  directives, are not mistaken for dollar-quoted literals.
  (#5905)

• Fixed query sanitization of PostgreSQL binary/octal literals and digit
  separators, MySQL binary literals, SQLite digit separators, Oracle
  floating-point suffixes, and hexadecimal literals with supported unary
  operators.
  (#5905)

• Fixed literals being left unsanitized in malformed SQL Server queries when
  escaped brackets extend an identifier beyond its 128-character limit.
  (#5905)

• Fixed MySQL and MariaDB query sanitization so that adjacent minus signs
  are not mistaken for a comment without following whitespace, and a lone
  carriage return does not end a line comment.
  (#5905)

• Fixed literals inside MySQL and MariaDB executable comments being left
  unsanitized. The remainder of a query after /*! or /*M! is now omitted
  because its boundary depends on the server version.
  (#5905)

See CHANGELOG for details.