Varnish Otel 3.0.0 Release

varnish-otel 3.0.0 is a breaking release. The exported log record body now always matches what varnishlog-json produces, byte for byte, instead of a re-marshaled struct — anything parsing the body as a fixed JSON shape should re-check it. Log records also no longer carry SpanId/TraceId/TraceFlags as string attributes; use the record’s own TraceID/SpanID/TraceFlags fields instead, which every exporter already sets natively.

Other changes:

• SeverityNumber is now set on every exported log record (traffic and probe logs), so backends can filter and alert on severity.
• Failed transactions (VSL error or 5xx response) now correctly set the OTel span Status to Error.
• Transaction errors reported by varnishlog-json are no longer silently dropped — severity, span error status, and error.type/error.message attributes now populate correctly for failed transactions.
• Prometheus metric families that collapse several raw counters onto one name no longer randomly drop the description on some scrapes.
• Reduced CPU and memory overhead in metrics recording, attribute handling, and duration calculation.

References

• varnish-otel changelog