audit_trail 1.0.0-alpha16

Every chained row now records the trace ID of the request or job that wrote it, and a new submodule fills it from OpenTelemetry. The two identifiers a row can carry, correlation_id and trace_id, are now transient data.

Upgrading

The audit_trail and audit_trail_outbox tables have a new trace_id column, and there is no update hook until the first beta release: reinstall the module to upgrade.

New

• Trace ID on every chained row (#3620443). The writer asks the new audit_trail.trace_id_provider service for the current W3C trace ID and stores it in an indexed trace_id column, whatever path wrote the entry. The base module's provider returns NULL; a module that knows the current trace decorates it. The entries list has a Trace ID filter, and an entry's detail page links its trace ID to that list.
• audit_trail_opentelemetry submodule (#3620442). Supplies the trace ID of the current OpenTelemetry span. It needs the open-telemetry/api library (composer require open-telemetry/api) and something that starts spans, such as the OpenTelemetry module. Its README explains why a trace ID continued from an incoming traceparent header is chosen by the client.
• Account name on account events (#3620441). Every audit_trail_user_auth row about a known account names it under account_name, in the transient bucket, so a row still says whose account it was after the account is deleted.

Changed

• correlation_id and trace_id are transient data (#3620443). Either can carry personal data: a trace ID continued from an incoming header is the client's, and a correlation ID is whatever the caller chose. Neither is signed. The transient purge clears both together with context_transient, and an archive carries them only while they are still set, so a row restored from an archive gets them back.

Fixed

• Interface strings (#3620444). The retention-delay units and the TSA verification messages can now be translated. Strings made only of placeholders are gone. Every label writes ID in capitals, so the detail page and the filter form share one string per label. A unit test now fails on any translation call whose string an extractor cannot read.
• Documentation (#3620445). The configuration guide documents the bundled severity filter, and lists the settings every filter shares in one place.