search

open-telemetry / semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains
Apache License 2.0
283 stars 175 forks source link

Generalize `db.query.parameter.<key>` to `db.operation.parameter.<key>` #1559

Closed trask closed 1 week ago

trask commented 2 weeks ago

Generalize db.query.parameter.<key> to db.operation.parameter.<key>, so that it can be used also for stored procedure parameters as well (and maybe other kinds of operations?)

Note: I don't think(?) schema transforms support attribute type template[string]

lmolkova commented 2 weeks ago

Note: I don't think(?) schema transforms support attribute type template[string]

@lquerel this is another data point on schema transformation limitations. Do we have an existing tracking issue I can update to include it?

lquerel commented 2 weeks ago

@lmolkova, we have two GitHub issues related to this topic:

  1. Why we need to change the way the OTEL Schema is specified: Limitations and evolution of the OpenTelemetry Schema file.
  2. The diff format I’m proposing, which could serve as the basis for a migration guide, schema update, etc.: Diff between two versions of a semconv registry - Proposal.

It would be great to get your feedback on one or both of these issues, especially in light of the discussions in the current PR.

Note: I don't think(?) schema transforms support attribute type template[string]

@lquerel this is another data point on schema transformation limitations. Do we have an existing tracking issue I can update to include it?