+
+ | Parameter
+ |
+ Comments
+ |
+
+
+
+ storage:
+ azure:
+ use_v2_sdk:
+ |
+ Removed. Azure v2 is the only and primary Azure backend [PR 3875]
+ |
+
+
+ autocomplete_filtering_enabled
+ |
+ The feature flag option has been removed. The feature is always enabled. [PR 3729]
+ |
+
+
+ completedfilepath and blocksfilepath
+ |
+ Removed unused WAL configuration options. [PR 3911]
+ |
+
+
+ compaction_disabled
+ |
+ New. Allow compaction disablement per-tenant. [PR 3965, documentation]
+ |
+
+
+
+
+Storage:
+ s3:
+ [enable_dual_stack: <bool>]
+ |
+ Boolean flag to activate or deactivate dualstack mode on the Storage block configuration for S3. [PR 3721, documentation]
+ |
+
+
+
+## Bugfixes
+
+For a complete list, refer to the [Tempo changelog](https://github.com/grafana/tempo/releases).
+
+* Fix panic in certain metrics queries using `rate()` with `by`. [[PR 3847](https://github.com/grafana/tempo/pull/3847)]
+* Fix metrics queries when grouping by attributes that may not exist. [[PR 3734](https://github.com/grafana/tempo/pull/3734)]
+* Fix metrics query histograms and quantiles on `traceDuration`. [[PR 3879](https://github.com/grafana/tempo/pull/3879)]
+* Fix divide by 0 bug in query frontend exemplar calculations. [[PR 3936](https://github.com/grafana/tempo/pull/3936)]
+* Fix autocomplete of a query using scoped instrinsics. [[PR 3865](https://github.com/grafana/tempo/pull/3865)]
+* Improved handling of complete blocks in localblocks processor after enabling flushing. [[PR 3805](https://github.com/grafana/tempo/pull/3805)]
+* Fix double appending the primary iterator on second pass with event iterator. [[PR 3903](https://github.com/grafana/tempo/pull/3903)]
+* Fix frontend parsing error on cached responses [[PR 3759](https://github.com/grafana/tempo/pull/3759)]
+* `max_global_traces_per_user`: take into account `ingestion.tenant_shard_size` when converting to local limit. [[PR 3618](https://github.com/grafana/tempo/pull/3618)]
+* Fix HTTP connection reuse on GCP and AWS by reading `io.EOF` through the `http` body. [[PR 3760](https://github.com/grafana/tempo/pull/3760)]
+* Handle out of boundaries spans kinds. [[PR 3861](https://github.com/grafana/tempo/pull/3861)]
+* Maintain previous tenant blocklist on tenant errors. [PR 3860](https://github.com/grafana/tempo/pull/3860)
+* Fix prefix handling in Azure backend `Find()` call. [[PR 3875](https://github.com/grafana/tempo/pull/3875)]
+* Correct block end time when the ingested traces are outside the ingestion slack. [[PR 3954](https://github.com/grafana/tempo/pull/3954)]
+* Fix race condition where a streaming response could be marshaled while being modified in the combiner resulting in a panic. [[PR 3961](https://github.com/grafana/tempo/pull/3961)]
+* Pass search options to the backend for `SearchTagValuesBlocksV2` requests. [[PR 3971](https://github.com/grafana/tempo/pull/3971)]
diff --git a/docs/sources/tempo/setup/upgrade.md b/docs/sources/tempo/setup/upgrade.md
index cdaf72838cc..e3f13c549a9 100644
--- a/docs/sources/tempo/setup/upgrade.md
+++ b/docs/sources/tempo/setup/upgrade.md
@@ -7,16 +7,140 @@ weight: 310
# Upgrade your Tempo installation
-You can upgrade an existing Tempo installation to the next version. However, any new release has the potential to have breaking changes that should be tested in a non-production environment prior to rolling these changes to production.
+You can upgrade an existing Tempo installation to the next version.
+However, any new release has the potential to have breaking changes that should be tested in a non-production environment prior to rolling these changes to production.
The upgrade process changes for each version, depending upon the changes made for the subsequent release.
This upgrade guide applies to on-premise installations and not for Grafana Cloud.
+For detailed information about any release, refer to the [Release notes](../release-notes/).
+
{{< admonition type="tip" >}}
You can check your configuration options using the [`status` API endpoint]({{< relref "../api_docs#status" >}}) in your Tempo installation.
{{% /admonition %}}
+## Upgrade to Tempo 2.6
+
+Tempo 2.5 has several considerations for any upgrade:
+
+* Operational change for TraceQL metrics
+* vParquet4 is now the default block format
+* Updated, removed, or renamed parameters
+
+For a complete list of changes, refer to the [Temopo 2.6 changelog](https://github.com/grafana/tempo/releases/tag/v2.6.0).
+
+### Operational change for TraceQL metrics
+
+We've changed to an RF1 (Replication Factor 1) pattern for TraceQL metrics as we were unable to hit performance goals for RF3 de-duplication. This requires some operational changes to query TraceQL metrics.
+
+TraceQL metrics are still considered experimental, but we hope to mark them GA soon when we productionize a complete RF1 write-read path. [PRs [3628](https://github.com/grafana/tempo/pull/3628), [3691]([https://github.com/grafana/tempo/pull/3691](https://github.com/grafana/tempo/pull/3691)), [3723]([https://github.com/grafana/tempo/pull/3723](https://github.com/grafana/tempo/pull/3723)), [3995]([https://github.com/grafana/tempo/pull/3995](https://github.com/grafana/tempo/pull/3995))]
+
+**For recent data**
+
+The local-blocks processor must be enabled to start using metrics queries like `{ } | rate()`. If not enabled metrics queries fail with the error `localblocks processor not found`. Enabling the local-blocks processor can be done either per tenant or in all tenants.
+
+* Per-tenant in the per-tenant overrides:
+
+ ```yaml
+ overrides:
+ 'tenantID':
+ metrics_generator_processors:
+ - local-blocks
+ ```
+
+* By default, for all tenants in the main config:
+
+ ```yaml
+ overrides:
+ defaults:
+ metrics_generator:
+ processors: [local-blocks]
+ ```
+
+Add this configuration to run TraceQL metrics queries against all spans (and not just server spans):
+
+```yaml
+metrics_generator:
+ processor:
+ local_blocks:
+ filter_server_spans: false
+```
+
+**For historical data**
+
+To run metrics queries on historical data, you must configure the local-blocks processor to flush rf1 blocks to object storage:
+
+```yaml
+metrics_generator:
+ processor:
+ local_blocks:
+ flush_to_storage: true
+```
+
+### Transition to vParquet4
+
+vParquet4 format is now the default block format.
+It's production ready and we highly recommend switching to it for improved query performance. [PR [3810](https://github.com/grafana/tempo/pull/3810)]
+
+Upgrading to Tempo 2.6 modifies the Parquet block format.
+Although you can use Tempo 2.6 with vParquet2 or vParquet3, you can only use Tempo 2.6 with vParquet3.
+
+You can also use the `tempo-cli analyse blocks` command to query vParquet4 blocks. [PR 3868](https://github.com/grafana/tempo/pull/3868)].
+Refer to the [Tempo CLI ](https://grafana.com/docs/tempo/next/operations/tempo_cli/#analyse-blocks)documentation for more information.
+
+For information on upgrading, refer to [Upgrade to Tempo 2.6](https://grafana.com/docs/tempo/next/setup/upgrade/) and [Choose a different block format](https://grafana.com/docs/tempo/next/configuration/parquet/#choose-a-different-block-format).
+
+### Updated, removed, or renamed configuration parameters
+
+
+
+ | Parameter
+ |
+ Comments
+ |
+
+
+ storage:
+
+ azure:
+
+ use_v2_sdk:
+ |
+ Removed. Azure v2 is the only and primary Azure backend [PR #3875]
+ |
+
+
+ autocomplete_filtering_enabled
+ |
+ The feature flag option has been removed. The feature is always enabled. [PR #3729]
+ |
+
+
+ completedfilepath and blocksfilepath
+ |
+ Removed unused WAL configuration options. [PR #3911]
+ |
+
+
+ compaction_disabled
+ |
+ New. Allow compaction disablement per-tenant. [PR #3965, documentation]
+ |
+
+
+ Storage:
+
+ s3:
+
+ [enable_dual_stack: <bool>]
+ |
+ Boolean flag to activate or deactivate dualstack mode on the Storage block configuration for S3. [PR #3721, documentation]
+ |
+
+
+
+
## Upgrade to Tempo 2.5
Tempo 2.5 has several considerations for any upgrade:
@@ -26,7 +150,7 @@ Tempo 2.5 has several considerations for any upgrade:
* Experimental vParquet4 block format
* Removed configuration parameters
-For a complete list of changes, enhancements, and bug fixes, refer to the [Tempo 2.5 changelog](https://github.com/).
+For a complete list of changes, enhancements, and bug fixes, refer to the [Tempo 2.5 changelog](https://github.com/grafana/tempo/releases/tag/v2.5.0).
### Docker image runs as new UID
@@ -89,7 +213,6 @@ To try vParquet4, refer to [Choose a block format](https://grafana.com/docs/temp
* Updating to OTLP 1.3.0 removes the deprecated `InstrumentationLibrary` and `InstrumentationLibrarySpan` from the OTLP receivers. [PR 3649](https://github.com/grafana/tempo/pull/3649)]
* Removes the addition of a tenant in multitenant trace id lookup. [PR 3522](https://github.com/grafana/tempo/pull/3522)]
-
## Upgrade to Tempo 2.4
Tempo 2.4 has several considerations for any upgrade: