diff --git a/docs/sources/tempo/traceql/metrics-queries/_index.md b/docs/sources/tempo/traceql/metrics-queries/_index.md
index 9f4c2a2fe77..af5fde0fde2 100644
--- a/docs/sources/tempo/traceql/metrics-queries/_index.md
+++ b/docs/sources/tempo/traceql/metrics-queries/_index.md
@@ -56,14 +56,14 @@ To run TraceQL metrics queries in Grafana, you need Grafana Cloud or Grafana 10.
 No extra configuration is needed.
 Use a Tempo data source that points to a Tempo database with TraceQL metrics enabled.
 
-Refer to [Solve problems using metrics queries](./solve-problems-metrics-queries/) for some real-world examples.
+Refer to [Solve problems using metrics queries](https://grafana.com/docs/tempo/<TEMPO_VERSION>/traceql/metrics-queries/solve-problems-metrics-queries/) for some real-world examples.
 
 ### Functions
 
 TraceQL metrics queries currently include the following functions for aggregating over groups of spans: `rate`, `count_over_time`, `quantile_over_time`, `histogram_over_time`, and `compare`.
 These functions can be added as an operator at the end of any TraceQL query.
 
-For detailed information and example queries for each function, refer to [TraceQL metrics functions](./functions).
+For detailed information and example queries for each function, refer to [TraceQL metrics functions](https://grafana.com/docs/tempo/<TEMPO_VERSION>/traceql/metrics-queries/functions/).
 
 ### Exemplars
 
diff --git a/docs/sources/tempo/traceql/metrics-queries/solve-problems-metrics-queries.md b/docs/sources/tempo/traceql/metrics-queries/solve-problems-metrics-queries.md
index 7f2c65730c8..fbd72df19b8 100644
--- a/docs/sources/tempo/traceql/metrics-queries/solve-problems-metrics-queries.md
+++ b/docs/sources/tempo/traceql/metrics-queries/solve-problems-metrics-queries.md
@@ -19,7 +19,7 @@ This page provides an example of how you can investigate the rate of incoming re
 
 The Tempo metrics-generator emits metrics with pre-configured labels for Rate, Error, and Duration (RED) metrics and service graph edges.
 Generated metric labels vary, but always include the service name (in service graph metrics, as a client and/or a server type).
-For more information, refer to the [metrics-generator documentation](../../metrics-generator/).
+For more information, refer to the [metrics-generator documentation](https://grafana.com/docs/tempo/<TEMPO_VERSION>/metrics-generator/).
 
 You can use these metrics to get an overview of application performance.
 The metrics can be directly correlated to the trace spans that are available for querying.