A pure translation table from xqlite's telemetry events to OpenTelemetry's stable database semantic-convention attributes.

xqlite has NO OpenTelemetry dependency — you own the handler and the SDK. Feed any [:xqlite, ...] event through attributes/3 inside your own :telemetry handler and attach the returned map to the span you create; backends with database-aware tooling (latency by statement, DB overview pages) key off exactly these names.

def handle_event([:xqlite | _] = event, measurements, metadata, _cfg) do
  attrs = Xqlite.Telemetry.OpenTelemetry.attributes(event, measurements, metadata)
  # create/end your OTel span here, with `attrs` as span attributes
end

Targets the STABLE database conventions: db.system.name, db.query.text, db.operation.name, db.namespace, error.type. Keys are strings, values strings — ready for OTel attribute APIs.

If first-class instrumentation lands later (an optional opentelemetry_api dependency, or a companion instrumentation package), it builds on this module as its attribute vocabulary — the mapping here is the contract either way.

Sources

Every mapped name traces to the OpenTelemetry specification:

• Database client spans (attribute set, the span-name priority chain, and the sqlite value for db.system.name): https://opentelemetry.io/docs/specs/semconv/database/database-spans/
• The db.* attribute registry (definitions of db.system.name, db.query.text, db.operation.name, db.namespace): https://opentelemetry.io/docs/specs/semconv/registry/attributes/db/
• The error.type attribute (general registry): https://opentelemetry.io/docs/specs/semconv/registry/attributes/error/

Verified against the stable revision of the database conventions on 2026-07-17; the pre-stabilization names (db.system, db.statement) are deliberately NOT emitted.