chore(deps): update docker.io/victoriametrics/victoria-traces docker tag to v0.11.0

[renovate]

This PR contains the following updates:

Package	Update	Change
docker.io/victoriametrics/victoria-traces	minor	v0.4.0 → v0.11.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

VictoriaMetrics/VictoriaTraces (docker.io/victoriametrics/victoria-traces)

v0.11.0

Compare Source

Released at 2026-08-14

• BUGFIX: cluster version: evenly spread rerouted data across available vtstorage nodes. Previously, healthy nodes adjacent to unavailable nodes in the -storageNode list could receive much more data, resulting in uneven resource usage. See this issue #​228.

• FEATURE: vtagent: introduce basic vtagent which accepts OTLP ingestion, and writes the formatted spans to /insert/native API. Check vtagent doc for details.

v0.10.0

Compare Source

Released at 2026-07-22

Update note 1: the base Docker image has been changed from Alpine to distroless in order to reduce an attack surface (The distroless base image doesn't contain any executables contrary to the Alpine base image). For debugging VictoriaTraces containers in Kubernetes it is recommended to use kubectl debug.

Update note 2: VictoriaTraces no longer provides a Docker image for the linux/386 platform because the distroless base image doesn't support this platform. Executable files for linux/386 platform are still published at the VictoriaTraces releases page.

• SECURITY: upgrade Go builder from Go1.26.4 to Go1.26.5. See the list of issues addressed in Go1.26.5.

• FEATURE: switch base Docker image from Alpine to distroless. This reduces the image size and attack surface. See the issue #​182 and issue #​1228 in VictoriaLogs.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: unify the command-line flags for configuring the lookbehind window of stream fields and fields search APIs with -search.fieldsLookbehind (default 2 hours) and -search.streamFieldsLookbehind (default 3 days). The old flag -search.traceServiceAndSpanNameLookbehind is now deprecated.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return span kinds in strings (internal, client, server, etc.) rather than integers for the Tempo /api/v2/search/tag/status/values endpoint; also add support for span kind transformation in TraceQL. Thank @​pkieszcz for reporting the issue #​200.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: correctly apply condition filters in the Tempo search API when searching for related spans. Previously, complex conditions such as pipe and trace duration (join query) were used as subqueries, which caused the trace duration filter to fail. See this issue #​218.

v0.9.4

Compare Source

Released at 2026-07-03

Update Note 1: cluster version: this release bumps the internal vtselect and vtstorage protocol version (see the queries-longer-than-10MB fix in VictoriaLogs #​1462). Any version mismatch between vtselect and vtstorage will cause requests to fail, meaning queries will error out during a rolling upgrade when the cluster runs mixed component versions. All components must be upgraded if you want to upgrade to this release or later.

• SECURITY: upgrade Go builder from Go1.26.3 to Go1.26.4. See the list of issues addressed in Go1.26.4.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.50.0 to v1.51.0.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: support configuring max traces limit for Jaeger and Tempo search traces APIs. Previously each API has default limit 20, and a hardcoded limit 1000 to prevent users from requesting an excessively large limit query argument.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: unify the command-line flags for configuring the maximum tags limit used in tags (tag values), service name, and span name search APIs with -search.maxTags. The old flags -search.traceMaxServiceNameList and -search.traceMaxSpanNameList are now deprecated.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return intrinsic span fields (name, kind, status, duration) under the intrinsic scope of the Tempo /api/v2/search/tags endpoint, and support scope=intrinsic. Previously these fields were missing (they have no attribute prefix and were skipped during tag discovery, and scope=intrinsic returned an error), so they did not appear in the Grafana Traces Drilldown attribute breakdown. Thank @​vshulakov-sh for the pull request #​175.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return proper spans with within spanSets for the Tempo /api/search API. Previously, this API only returned root spans. This enables trace span focus by span ID when viewing a trace. See the pull request #​201 for details. Thank @​yusufcemalcelebi for reporting the issue and proposing the change.

v0.9.3

Compare Source

Released at 2026-06-18

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: support the Tempo querying traces by id (v1) endpoint /api/traces/<trace_id>. Previously only the v2 /api/v2/traces/<trace_id> endpoint was served.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: honor the Accept header on the Tempo traces by id endpoints (v1 and v2). These endpoints now return OTLP/JSON by default, and return protobuf when Accept: application/protobuf header is set.

• FEATURE: Single-node VictoriaTraces and vtstorage in VictoriaTraces cluster: expose filesystem type for storage paths via the vm_fs_info metric. This helps identify filesystem-specific issues during troubleshooting. See #​164 for details.

• BUGFIX: Single-node VictoriaTraces and vtinsert in VictoriaTraces cluster: response empty partial success correctly when error message for OTLP ingestion is empty. Thank @​immanuwell for the pull request #​170.

v0.9.2

Compare Source

Released at 2026-06-01

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: exclude unnecessary streams during trace search. These streams caused empty trace_id values in subsequent queries and parsing errors. This issue was introduced since v0.4.0.

v0.9.1

Compare Source

Released at 2026-06-01

• SECURITY: upgrade Go builder from Go1.26.2 to Go1.26.3. See the list of issues addressed in Go1.26.3.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.47.0 to v1.50.0.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: extend TraceQL support for fuzzy match and regex syntax. Thank @​vshulakov-sh for the pull request #​158.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return span status in string (unset, ok, error) instead of integers (0, 1, 2) in Tempo /api/v2/search/tag/status/values endpoint. Thank @​vshulakov-sh for the pull request #​155.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: populate spanSets in the Tempo /api/search response with a synthesized root span (spanID, startTimeUnixNano, durationNanos, and service.name/nestedSetParent attributes) to allow Grafana Traces Drilldown plugin show traces. Thank @​vshulakov-sh for the pull request #​162.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: safeguard duration calculation for the Tempo search API when start or end time is missing. Previously, the value could exceed the int32 range and cause display errors. See pull request #​153 for details.

v0.9.0

Compare Source

Released at 2026-05-20

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: (experimental) extend Tempo API support for Grafana Traces Drilldown. Thank @​vshulakov-sh for the pull request #​132.
• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: add ability to hide the given span attributes on a per-query basis. This may be useful for restricting access to span attributes with sensitive information, by specifying the list of the fields to hide via hidden_fields_filters query arg. See these docs for details.

v0.8.2

Compare Source

Released at 2026-04-27

• SECURITY: upgrade base docker image (Alpine) from 3.23.3 to 3.23.4. See Alpine 3.23.4 release notes.

• BUGFIX: Single-node VictoriaTraces and vtinsert in VictoriaTraces cluster: fix OTLP/gRPC failure with TLS enabled during HTTP/2 ALPN negotiation. See #​108 for details. Thank @​hklhai for the pull request #​136.

• BUGFIX: Single-node VictoriaTraces and vtinsert in VictoriaTraces cluster: fix parsing error for OTLP/JSON when numeric values are passed as numbers instead of strings. See #​134 for details.

v0.8.1

Compare Source

Released at 2026-04-14

• SECURITY: upgrade Go builder from Go1.26.0 to Go1.26.2. See the list of issues addressed in Go1.26.1 and Go1.26.2.

• FEATURE: Single-node VictoriaTraces and vtstorage in VictoriaTraces cluster: allow generating service graph relation by database client span. The client span contains db.system.name attribute will generate a service.name:db.system.name (example: account_service:mysql) relation. It can be disabled by setting -servicegraph.databaseTaskLimit=0. Thank @​wsx864321 for the pull request #​117.

• FEATURE: dashboards/single-node, dashboards/cluster: add clickable source code links to the Logging rate panel in Overview. Users can use it to navigate directly to the source code location that generated those logs, making debugging and code exploration easier. See #​106.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: support positive regex matching in the Jaeger query API when filtering traces by tags. See the pull request #​116 for examples. Thank @​emamihe for the pull request.

v0.8.0

Compare Source

Released at 2026-03-02

• SECURITY: upgrade Go builder from Go1.25.5 to Go1.26.0. See the list of issues addressed in Go1.26.0.

• SECURITY: upgrade base docker image (Alpine) from 3.22.2 to 3.23.3. See Alpine 3.23.3 release notes.

• BUGFIX: fix VictoriaTraces Docker OCI labels org.opencontainers.image.source and org.opencontainers.image.documentation: point them to VictoriaTraces repo/docs instead of VictoriaMetrics.

• FEATURE: Single-node VictoriaTraces and vtselect, vtstorage in VictoriaTraces cluster: (experimental) add support for Tempo datasource APIs. This starts with support for the basic auto-completion /tags, search /search, and /v2/traces/* APIs. TraceQL metrics and pipelines are not yet available in this release.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.43.1 to v1.47.0.

v0.7.1

Compare Source

Released at 2026-01-24

• FEATURE: Single-node VictoriaTraces and vtstorage in VictoriaTraces cluster: adjust -insert.indexFlushInterval from 30s to 20s to ensure a proper time gap with -search.latencyOffset. This is useful when ingest data is not real-time, as it helps reduce the probability that data can be searched by condition but is not present in the traceID index, resulting in failure to query by traceID.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: fix backward compatibility for the old index format. Previously, the old index format was not parsed correctly into the start and end timestamps.

v0.7.0

Compare Source

Released at 2026-01-21

• FEATURE: Single-node VictoriaTraces and VictoriaTraces cluster: add duration and error metrics for service graph background tasks. Thank @​chenlujjj for the pull request #​100.
• FEATURE: Single-node VictoriaTraces and VictoriaTraces cluster: add accurate start time and end time to the trace ID index. This should help with the trace lookup by ID, and will free user from configuring -search.traceMaxDurationWindow to avoid missing the spans. See the pull request #​81.

v0.6.0

Compare Source

Released at 2026-01-07

• SECURITY: upgrade Go builder from Go1.25.4 to Go1.25.5. See the list of issues addressed in Go1.25.5.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.38.0 to v1.43.1.

• FEATURE: Single-node VictoriaTraces and vtinsert in VictoriaTraces cluster: reduce CPU usage of the OpenTelemetry protobuf data ingestion in both OTLP/HTTP and OTLP/gRPC APIs. Thanks to @​vadimalekseev for the initial idea.

v0.5.1

Compare Source

Released at 2025-11-19

• SECURITY: upgrade Go builder from Go1.25.3 to Go1.25.4. See the list of issues addressed in Go1.25.4.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.36.1 to v1.38.0.

• BUGFIX: Single-node VictoriaTraces and vtinsert in VictoriaTraces cluster: properly apply maxDataSize memory limits to the snappy and zstd encoded requests. It protects ingest endpoints from malicious requests.

v0.5.0

Compare Source

Released at 2025-11-08

• SECURITY: upgrade Go builder from Go1.25.2 to Go1.25.3. See the list of issues addressed in Go1.25.3.

• FEATURE: Single-node VictoriaTraces and VictoriaTraces cluster: support OTLP/gRPC data ingestion. It requires -otlpGRPCListenAddr flag to be set on Single-node VictoriaTraces or vtinsert. See this doc for details. Thanks to @​JayiceZ for the pull request.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return the correct error message and the total number when searching by trace ID yields no hits in the result. Thank @​huan89983 for the bug report.

v0.4.1

Compare Source

Released at 2025-10-31

• FEATURE: add linux/s390x artifact to releases.

• BUGFIX: Single-node VictoriaTraces and VictoriaTraces cluster: stop query at the earlier timestamp of the retention period when searching by a non-existed trace ID, and response earlier. See #​48 for details. Thank @​JayiceZ for the pull request.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.