Project: Grafana Tempo (Observability and Analysis / Observability)
File: v1-5.md

title: Version 1.5 release notes menuTitle: V1.5 description: Release notes for Grafana Tempo 1.5 weight: 70 The Tempo team is pleased to announce the release of Tempo 1.5. With this release, Tempo adds experimental support for a new trace storage format based on , anonymous usage reporting to help the Tempo team understand how Tempo is used, and enhancements to the metrics-generator. We encourage users to upgrade to to take advantage of new Tempo-powered capabilities, such as the which visualizes span metrics (traces data for rates, error rates, and durations (RED)) and service graphs. Note: For a complete list of changes and enhancements, refer to the . Version 1.5 contains the following features and enhancements. Tempo now supports a columnar block format for trace storage based on . We're excited about this new format because it will enable increased speed and efficiency for Tempo search. It also allows users to leverage the large ecosystem of existing Parquet tools and libraries to process and transform their trace data. We're releasing the Parquet block format as experimental in Tempo 1.5, with plans to move it to stable in a future release once we've had more opportunity to test it. The new Parquet block format can be used as a drop-in replacement for Tempo's existing block format. No data conversion or upgrade process is necessary. As soon as the Parquet format is enabled, Tempo starts writing data in that format, leaving existing data as-is. For more information, refer to the . Please note, however, that enabling the Parquet block format means Tempo will require more CPU and memory resources than it previously did. To use Parquet, set the block format option to `vParquet` in the configuration file. Refer to the and the . ```yaml [version: <string> | default = v2] ``` For more information about the Parquet implementation, refer to the and . The now includes databases and requests across messaging systems in service graph metrics. The OpenTelemetry semantic conventions are used to detect when a span is involved in one of these systems. In addition, metrics-generator supports per-tenant processor

By default, Tempo will report anonymous usage data about itself to Grafana Labs. This data is used to understand which features are commonly enabled, as well as which deployment modes, replication factors, and compression levels are most popular, etc. By providing information on how people use Tempo, usage reporting helps the Tempo team decide where to focus their development and documentation efforts. No private information is collected, and all reports are completely anonymous. Reporting is controlled by the `usage_report` configuration option and can be disabled. For instructions, refer to . When upgrading to Tempo v1.5, be aware of these breaking changes: To build advanced visualization features into Grafana, we have decided to change our spanmetric names to match OpenTelemetry (OTel) conventions. Any functionality added to Grafana will work whether you use Tempo, Grafana Agent, or the OTel Collector to generate metrics. The old histogram metric name in Tempo 1.4.x: ``` tracesspanmetricsdurationseconds{sum,count,bucket} ``` has been replaced with this new name in Tempo 1.5: ``` tracesspanmetricslatency_{sum,count,bucket} ``` Additionally, the default label `spanstatus` has been renamed to `statuscode`. Jsonnet users will need to specify ephemeral storage requests and limits for the metrics generator. ``` _config+:: { metrics_generator+: { ephemeralstoragerequest_size: '10Gi', ephemeralstoragelimit_size: '11Gi', }, } ``` As a result of the anonymous usage reporting feature, distributors and metrics-generators now require the same level of access to object storage as compactors and ingesters. Users who disable anonymous usage reporting are exempt from this requirement. Deprecated metrics `tempodb(gcs|s3|azure)requestdurationseconds` have been removed in favor of `tempodbbackendrequestdurationseconds`. These metrics have been deprecated since v1.1. Version 1.5.0 includes the following fixes: Fixed nil pointer panic when the trace by id path errors. Updated Tempo microservices Helm values example which missed the `enabled` key for thriftHttp. Fixed race condition in forwarder overrides loop. Fixed v2 backend check on span name to be substring. Fixed wal check on span name to be substring. Prevented the ingester panic "cannot grow buffer". metrics-generator: do not remove `x-scope-orgid header` in single tenant modus. Fixed an issue where backend does not support `root.name` and `root.service.name`. Fixed the ingester to continue starting up after block replay error.