[v2.7.x] Remove relref shortcodes (#4821)

* relref replace - tempo

* fix manifest link

Author: robbymilo

docs/sources/tempo/configuration/_index.md

@@ -52,7 +52,7 @@ The Tempo configuration options include:
   - [Usage-report](#usage-report)
   - [Cache](#cache)
 
-Additionally, you can review [TLS]({{< relref "./network/tls" >}}) to configure the cluster components to communicate over TLS, or receive traces over TLS.
+Additionally, you can review [TLS](network/tls/) to configure the cluster components to communicate over TLS, or receive traces over TLS.
 
 ## Use environment variables in the configuration
 
@@ -356,7 +356,7 @@ ingester:
 For more information on configuration options, refer to [this file](https://github.com/grafana/tempo/blob/main/modules/generator/config.go).
 
 The metrics-generator processes spans and write metrics using the Prometheus remote write protocol.
-For more information on the metrics-generator, refer to the [Metrics-generator documentation]({{< relref "../metrics-generator" >}}).
+For more information on the metrics-generator, refer to the [Metrics-generator documentation](../metrics-generator/).
 
 Metrics-generator processors are disabled by default. To enable it for a specific tenant, set `metrics_generator.processors` in the [overrides](#overrides) section.
 
@@ -970,10 +970,10 @@ The storage block configures TempoDB.
 The following example shows common options.
 For further platform-specific information, refer to the following:
 
-* [GCS]({{< relref "./hosted-storage/gcs" >}})
-* [S3]({{< relref "./hosted-storage/s3" >}})
-* [Azure]({{< relref "./hosted-storage/azure" >}})
-* [Parquet]({{< relref "./parquet" >}})
+* [GCS](hosted-storage/gcs/)
+* [S3](hosted-storage/s3/)
+* [Azure](hosted-storage/azure/)
+* [Parquet](parquet/)
 
 ```yaml
 # Storage configuration for traces

docs/sources/tempo/configuration/grafana-agent/_index.md

@@ -119,22 +119,22 @@ Refer to the `scrape_configs` block in the [configuration reference](/docs/agent
 
 Automatic logging writes well formatted log lines to help with trace discovery.
 
-For a closer look into the feature, visit [Automatic logging]({{< relref "./automatic-logging" >}}).
+For a closer look into the feature, visit [Automatic logging](automatic-logging/).
 
 #### Tail-based sampling
 
 The Agent implements tail-based sampling for distributed tracing systems and multi-instance Agent deployments.
 With this feature, sampling decisions can be made based on data from a trace, rather than exclusively with probabilistic methods.
 
-For a detailed description, go to [Tail-based sampling]({{< relref "./tail-based-sampling" >}}).
+For a detailed description, go to [Tail-based sampling](tail-based-sampling/).
 
 For additional information, refer to the blog post, [An introduction to trace sampling with Grafana Tempo and Grafana Agent](/blog/2022/05/11/an-introduction-to-trace-sampling-with-grafana-tempo-and-grafana-agent).
 
 #### Generating metrics from spans
 
 The Agent can take advantage of the span data flowing through the pipeline to generate Prometheus metrics.
 
-Go to [Span metrics]({{< relref "./span-metrics" >}}) for a more detailed explanation of the feature.
+Go to [Span metrics](span-metrics/) for a more detailed explanation of the feature.
 
 #### Service graph metrics
 
@@ -144,7 +144,7 @@ This service graphs processor builds a map of services by analyzing traces, with
 Edges are spans with a parent-child relationship, that represent a jump, such as a request, between two services.
 The amount of requests and their duration are recorded as metrics, which are used to represent the graph.
 
-To read more about this processor, go to its [section]({{< relref "./service-graphs" >}}).
+To read more about this processor, go to its [section](service-graphs/).
 
 ### Exporting spans
 

docs/sources/tempo/configuration/grafana-agent/service-graphs.md

@@ -17,10 +17,10 @@ and the connections and dependencies between its components.
 
 The same service graph metrics can also be generated by Tempo.
 This is more efficient and recommended for larger installations.
-For a deep look into service graphs, visit [this section]({{< relref "../../metrics-generator/service_graphs" >}}).
+For a deep look into service graphs, visit [this section](../../../metrics-generator/service_graphs/).
 
 Service graphs are also used in the application performance management dashboard.
-For more information, refer to the [service graph view documentation]({{< relref "../../metrics-generator/service-graph-view" >}}).
+For more information, refer to the [service graph view documentation](../../../metrics-generator/service-graph-view/).
 
 ## Before you begin
 
@@ -70,4 +70,4 @@ metrics:
 The same service graph metrics can also be generated by Tempo.
 This is more efficient and recommended for larger installations.
 
-For additional information about viewing service graph metrics in Grafana and calculating cardinality, refer to the [server side documentation]({{< relref "../../metrics-generator/service_graphs/enable-service-graphs" >}}).
+For additional information about viewing service graph metrics in Grafana and calculating cardinality, refer to the [server side documentation](../../../metrics-generator/service_graphs/enable-service-graphs/).

docs/sources/tempo/configuration/grafana-agent/span-metrics.md

@@ -40,7 +40,7 @@ For more information, refer to [Migrate to Alloy](https://grafana.com/docs/tempo
 
 The same span metrics can also be generated by Tempo.
 This is more efficient and recommended for larger installations.
-For a deep look into span metrics, visit [this section]({{< relref "../../metrics-generator/span_metrics" >}}).
+For a deep look into span metrics, visit [this section](../../../metrics-generator/span_metrics/).
 
 ## Example
 

docs/sources/tempo/configuration/hosted-storage/_index.md

@@ -11,6 +11,6 @@ aliases:
 
 Tempo provides additional hosted storage configuration options discussed on the pages below. These options relate to providers such as Google Cloud, AWS S3, and Azure.
 
-For additional details about storage configuration, refer to [Storage configuration]({{< relref "../../configuration#storage" >}}).
+For additional details about storage configuration, refer to [Storage configuration](../#storage).
 
 {{< section withDescriptions="true">}}

docs/sources/tempo/configuration/hosted-storage/gcs.md

@@ -7,7 +7,7 @@ aliases:
 
 # Google Cloud Storage
 
-For configuration options, check the storage section on the [configuration]({{< relref "../../configuration#storage" >}}) page.
+For configuration options, check the storage section on the [configuration](../../#storage) page.
 
 ## Permissions
 

docs/sources/tempo/configuration/hosted-storage/s3.md

@@ -8,7 +8,7 @@ aliases:
 
 # Amazon S3 permissions
 
-For configuration options, refer to the storage section on the [configuration]({{< relref "../../configuration#storage" >}}) page.
+For configuration options, refer to the storage section on the [configuration](../../#storage) page.
 
 The following authentication methods are supported:
 - AWS environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`

docs/sources/tempo/configuration/manifest.md

@@ -10,7 +10,7 @@ weight: 110
 
 This document is a reference for all Tempo options and their defaults. If you are just getting
 started with Tempo, refer to [Tempo examples](https://github.com/grafana/tempo/tree/main/example/docker-compose)
-and other [configuration documentation]({{< relref "../configuration" >}}). Most installations will require only setting 10 to 20 of these options.
+and other [configuration documentation](../). Most installations will require only setting 10 to 20 of these options.
 
 ## Complete configuration
 

docs/sources/tempo/configuration/parquet.md

@@ -8,7 +8,7 @@ weight: 300
 # Apache Parquet block format
 
 Tempo has a default columnar block format based on Apache Parquet.
-This format is required for tags-based search as well as [TraceQL]({{< relref "../traceql" >}}), the query language for traces.
+This format is required for tags-based search as well as [TraceQL](../../traceql/), the query language for traces.
 The columnar block format improves search performance and enables an ecosystem of tools, including [Tempo CLI](https://grafana.com/docs/tempo/<TEMPO_VERSION>/operations/tempo_cli/#analyse-blocks), to access the underlying trace data.
 
 For more information, refer to the [Parquet design document](https://github.com/grafana/tempo/blob/main/docs/design-proposals/2022-04%20Parquet.md) and [Issue 1480](https://github.com/grafana/tempo/issues/1480).
@@ -53,7 +53,7 @@ To re-enable the default `vParquet4` format, remove the block version option fro
 ## Parquet configuration parameters
 
 Some parameters in the Tempo configuration are specific to Parquet.
-For more information, refer to the [storage configuration documentation]({{< relref "../configuration#storage" >}}).
+For more information, refer to the [storage configuration documentation](../#storage).
 
 ### Trace search parameters
 

docs/sources/tempo/configuration/polling.md

@@ -35,7 +35,7 @@ storage:
         [blocklist_poll_stale_tenant_index: <duration>]
 ```
 
-Due to the mechanics of the [tenant index]({{< relref "../operations/monitor/polling" >}}), the blocklist will be stale by
+Due to the mechanics of the [tenant index](../../operations/monitor/polling/), the blocklist will be stale by
 at most 2 times the configured `blocklist_poll` duration. There are two configuration options that need to be balanced
 against the `blockist_poll` to handle this: