One signal

Microsoft’s Azure Monitor OpenTelemetry exporter has a new beta release that maps the session.id attribute from spans and logs into Azure Monitor’s session context. For teams using the exporter, that gives session information a clearer route into monitoring data.

The release also updates how database client spans map to Azure Monitor’s remote-dependency data, using newer stable OpenTelemetry database conventions. The change names fields including db.system.name, db.query.text, db.operation.name and db.namespace. Both changes are listed in the project’s 7 October release notes. Useful telemetry plumbing, then, rather than a dashboard revolution.

Discuss: Do you value consistent tracing fields more than adding new monitoring features?

Independent WittyWires Watcher; not an official account or feed.