[v10.0.x] [feat] docs; update admonition syntax (#68857)

[feat] docs; update admonition syntax (#68842) * [feat] docs; update admonition syntax - Standardizes according to style conventions: https://grafana.com/docs/writers-toolkit/style-guide/style-conventions/#admonitions - Prepares docs for better, uniform admonition style. * Remove false positives and irregularities * false positive removal * Update docs/sources/datasources/mysql/_index.md * Update docs/sources/developers/angular_deprecation/angular-plugins.md * fix link errors * Prettify some nested blockquotes * remoe unnecessary admonition (cherry picked from commit 1c4bb9ca00) Co-authored-by: Matt Dodson <47385188+MattDodsonEnglish@users.noreply.github.com>
2023-05-23 07:47:49 -05:00
parent defce65315
commit 1e8c28eff4
144 changed files with 1840 additions and 405 deletions
@@ -27,7 +27,9 @@ Administrators can also [provision the data source]({{< relref "#provision-the-d

 Once you've added the data source, you can [configure it]({{< relref "#configure-the-data-source" >}}) so that your Grafana instance's users can create queries in its [query editor]({{< relref "./query-editor/" >}}) when they [build dashboards]({{< relref "../../dashboards/build-dashboards/" >}}) and use [Explore]({{< relref "../../explore/" >}}).

-> **Note:** To troubleshoot issues while setting up the CloudWatch data source, check the `/var/log/grafana/grafana.log` file.
+{{% admonition type="note" %}}
+To troubleshoot issues while setting up the CloudWatch data source, check the `/var/log/grafana/grafana.log` file.
+{{% /admonition %}}

 ## Configure the data source

@@ -344,7 +346,9 @@ filter @message like /Exception/
    | sort exceptionCount desc
 ```

-> **Note:** If you receive an error like `input data must be a wide series but got ...` when trying to alert on a query, make sure that your query returns valid numeric data that can be output to a Time series panel.
+{{% admonition type="note" %}}
+If you receive an error like `input data must be a wide series but got ...` when trying to alert on a query, make sure that your query returns valid numeric data that can be output to a Time series panel.
+{{% /admonition %}}

 For more information on Grafana alerts, refer to [Alerting]({{< relref "../../alerting" >}}).

@@ -355,8 +359,10 @@ Pricing for CloudWatch Logs is based on the amount of data ingested, archived, a
 Each time you select a dimension in the query editor, Grafana issues a `ListMetrics` API request.
 Each time you change queries in the query editor, Grafana issues a new request to the `GetMetricData` API.

-> **Note:** Grafana v6.5 and higher replaced all `GetMetricStatistics` API requests with calls to GetMetricData to provide better support for CloudWatch metric math, and enables the automatic generation of search expressions when using wildcards or disabling the `Match Exact` option.
-> The `GetMetricStatistics` API qualified for the CloudWatch API free tier, but `GetMetricData` calls don't.
+{{% admonition type="note" %}}
+Grafana v6.5 and higher replaced all `GetMetricStatistics` API requests with calls to GetMetricData to provide better support for CloudWatch metric math, and enables the automatic generation of search expressions when using wildcards or disabling the `Match Exact` option.
+The `GetMetricStatistics` API qualified for the CloudWatch API free tier, but `GetMetricData` calls don't.
+{{% /admonition %}}

 For more information, refer to the [CloudWatch pricing page](https://aws.amazon.com/cloudwatch/pricing/).

@@ -77,7 +77,9 @@ For more information on why and how to use service endpoints, refer to the [AWS

 Create a file at `~/.aws/credentials`, the `HOME` path for the user running the `grafana-server` service.

-> **Note:** If you think you have the credentials file in the right location, but it's not working, try moving your `.aws` file to `/usr/share/grafana/` and grant your credentials file at most 0644 permissions.
+{{% admonition type="note" %}}
+If you think you have the credentials file in the right location, but it's not working, try moving your `.aws` file to `/usr/share/grafana/` and grant your credentials file at most 0644 permissions.
+{{% /admonition %}}

 ### Credentials file example

@@ -90,7 +90,9 @@ For details on the available functions, refer to [AWS Metric Math](https://docs.

 For example, to apply arithmetic operations to a metric, apply a unique string id to the raw metric, then use this id and apply arithmetic operations to it in the Expression field of the new metric.

-> **Note:** If you use the expression field to reference another query, like `queryA * 2`, you can't create an alert rule based on that query.
+{{% admonition type="note" %}}
+If you use the expression field to reference another query, like `queryA * 2`, you can't create an alert rule based on that query.
+{{% /admonition %}}

 #### Period macro

@@ -109,7 +111,9 @@ This feature is not available for metrics based on [metric math expressions](#me

 ### Create a Metric Insights query

-> **Note:** This query option is available only in Grafana v8.3 and higher.
+{{% admonition type="note" %}}
+This query option is available only in Grafana v8.3 and higher.
+{{% /admonition %}}

 The Metrics Query option in the CloudWatch data source is referred to as **Metric Insights** in the AWS console.
 It's a fast, flexible, SQL-based query engine that you can use to identify trends and patterns across millions of operational metrics in real time.
@@ -171,7 +175,9 @@ The suggestions appear after typing a space, comma, or dollar (`$`) character, o

 {{< figure src="/static/img/docs/cloudwatch/cloudwatch-code-editor-autocomplete-8.3.0.png" max-width="500px" class="docs-image--right" caption="Code editor autocomplete" >}}

-> **Note:** Template variables in the code editor can interfere with autocompletion.
+{{% admonition type="note" %}}
+Template variables in the code editor can interfere with autocompletion.
+{{% /admonition %}}

 To run the query, click **Run query** above the code editor.

@@ -92,7 +92,9 @@ Toggle this to enable `X-Pack`-specific features and options, which provide the

 When the "X-Pack enabled" setting is active and the configured Elasticsearch version is higher than `6.6.0`, you can configure Grafana to not ignore [frozen indices](https://www.elastic.co/guide/en/elasticsearch/reference/7.13/frozen-indices.html) when performing search requests.

-> **Note:** Frozen indices are [deprecated in Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/frozen-indices.html) since v7.14.
+{{% admonition type="note" %}}
+Frozen indices are [deprecated in Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/frozen-indices.html) since v7.14.
+{{% /admonition %}}

 ### Logs

@@ -126,7 +128,9 @@ For details on AWS SigV4, refer to the [AWS documentation](https://docs.aws.amaz

 #### AWS Signature Version 4 authentication

-> **Note:** Available in Grafana v7.3 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.3 and higher.
+{{% /admonition %}}

 To sign requests to your Amazon Elasticsearch Service domain, you can enable SigV4 in Grafana's [configuration]({{< relref "../../setup-grafana/configure-grafana/#sigv4_auth_enabled" >}}).

@@ -140,9 +144,11 @@ For more information about AWS authentication options, refer to [AWS authenticat
 You can define and configure the data source in YAML files as part of Grafana's provisioning system.
 For more information about provisioning, and for available configuration options, refer to [Provisioning Grafana]({{< relref "../../administration/provisioning/#data-sources" >}}).

-> **Note:** The previously used `database` field has now been [deprecated](https://github.com/grafana/grafana/pull/58647).
-> You should now use the `index` field in `jsonData` to store the index name.
-> Please see the examples below.
+{{% admonition type="note" %}}
+The previously used `database` field has now been [deprecated](https://github.com/grafana/grafana/pull/58647).
+You should now use the `index` field in `jsonData` to store the index name.
+Please see the examples below.
+{{% /admonition %}}

 #### Provisioning examples

@@ -47,7 +47,9 @@ These queries by default return results in term order (which can then be sorted
 To produce a list of terms sorted by doc count (a top-N values list), add an `orderBy` property of "doc_count".
 This automatically selects a descending sort.

-> **Note:** To use an ascending sort (`asc`) with doc_count (a bottom-N list), set `order: "asc"`. However, Elasticsearch [discourages this](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-order) because sorting by ascending doc count can return inaccurate results.
+{{% admonition type="note" %}}
+To use an ascending sort (`asc`) with doc_count (a bottom-N list), set `order: "asc"`. However, Elasticsearch [discourages this](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-order) because sorting by ascending doc count can return inaccurate results.
+{{% /admonition %}}

 To keep terms in the doc count order, set the variable's Sort dropdown to **Disabled**.
 You can alternatively use other sorting criteria, such as **Alphabetical**, to re-sort them.
@@ -24,7 +24,9 @@ weight: 350
 Grafana ships with built-in support for Google Cloud Monitoring.
 This topic describes queries, templates, variables, and other configuration specific to the Google Cloud Monitoring data source.

-> **Note:** Before Grafana v7.1, Google Cloud Monitoring was referred to as Google Stackdriver.
+{{% admonition type="note" %}}
+Before Grafana v7.1, Google Cloud Monitoring was referred to as Google Stackdriver.
+{{% /admonition %}}

 For instructions on how to add a data source to Grafana, refer to the [administration documentation]({{< relref "../../administration/data-source-management/" >}}).
 Only users with the organization administrator role can add data sources.
@@ -177,7 +177,9 @@ An expected result would look like: `gce_instance - compute.googleapis.com/insta

 ### Deep-link from Grafana panels to the Google Cloud Console Metrics Explorer

-> **Note:** Available in Grafana v7.1 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.1 and higher.
+{{% /admonition %}}

 {{< figure src="/static/img/docs/v71/cloudmonitoring_deep_linking.png" max-width="500px" class="docs-image--no-shadow" caption="Google Cloud Monitoring deep linking" >}}

@@ -199,7 +201,9 @@ If the query editor rows return different units, Grafana uses the unit from the

 ### Use the Monitoring Query Language

-> **Note:** Available in Grafana v7.4 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.4 and higher.
+{{% /admonition %}}

 The Monitoring Query Language (MQL) query builder helps you query and display MQL results in time series format.
 To understand basic MQL concepts, refer to [Introduction to Monitoring Query Language](https://cloud.google.com/monitoring/mql).
@@ -222,7 +226,9 @@ However, `{{metric.service}}` is not supported, and `{{metric.type}}` and `{{met

 ## Query Service Level Objectives

-> **Note:** Available in Grafana v7.0 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.0 and higher.
+{{% /admonition %}}

 {{< figure src="/static/img/docs/google-cloud-monitoring/slo-query-builder-8-0.png" max-width="400px" class="docs-image--no-shadow" caption="Service Level Objectives (SLO) query editor" >}}

@@ -66,8 +66,10 @@ Grafana consolidates all Graphite metrics so that Graphite doesn't return more d
 By default, Grafana consolidates data points using the `avg` function.
 To control how Graphite consolidates metrics, use the Graphite `consolidateBy()` function.

-> **Note:** Legend summary values (max, min, total) can't all be correct at the same time because they are calculated client-side by Grafana.
-> Depending on your consolidation function, only one or two can be correct at the same time.
+{{% admonition type="note" %}}
+Legend summary values (max, min, total) can't all be correct at the same time because they are calculated client-side by Grafana.
+Depending on your consolidation function, only one or two can be correct at the same time.
+{{% /admonition %}}

 ### Combine time series

@@ -82,8 +84,10 @@ To select data, use the `seriesByTag` function, which takes tag expressions (`=`

 The Grafana query builder does this for you automatically when you select a tag.

-> **Tip:** The regular expression search can be slow on high-cardinality tags, so try to use other tags to reduce the scope first.
-> To help reduce the results, start by filtering on a particular name or namespace.
+{{% admonition type="note" %}}
+The regular expression search can be slow on high-cardinality tags, so try to use other tags to reduce the scope first.
+To help reduce the results, start by filtering on a particular name or namespace.
+{{% /admonition %}}

 ## Nest queries

@@ -104,7 +104,9 @@ For example, `apps.$app.servers.*` uses the variable `$app` in its query definit

 ### Use `__searchFilter` to filter query variable results

-> **Note:** Available in Grafana v6.5 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v6.5 and higher.
+{{% /admonition %}}

 You can use `__searchFilter` in the query field to filter the query result based on what the user types in the dropdown select box.
 The default value for `__searchFilter` is `*` if you've not entered anything, and `` when used as part of a regular expression.
@@ -84,10 +84,13 @@ InfluxDB data source options differ depending on which query language you select

 To help choose the best language for your needs, refer to a [comparison of Flux vs InfluxQL](https://docs.influxdata.com/influxdb/v1.8/flux/flux-vs-influxql/) and [why InfluxData created Flux](https://www.influxdata.com/blog/why-were-building-flux-a-new-data-scripting-and-query-language/).

-> **Note:** Though not required, we recommend that you append your query language choice to the data source's **Name** setting:
->
-> - InfluxDB-InfluxQL
-> - InfluxDB-Flux
+{{% admonition type="note" %}}
+Though not required, we recommend that you append your query language choice to the data source's **Name** setting:
+
+- InfluxDB-InfluxQL
+- InfluxDB-Flux
+
+{{% /admonition %}}

 ### Configure InfluxQL

@@ -117,9 +120,11 @@ Configure these options if you select the Flux query language:
 You can define and configure the data source in YAML files as part of Grafana's provisioning system.
 For more information about provisioning, and for available configuration options, refer to [Provisioning Grafana]({{< relref "../../administration/provisioning/#data-sources" >}}).

-> **Note:** `database` [field is deprecated](https://github.com/grafana/grafana/pull/58647).
-> We suggest to use `dbName` field in `jsonData`. Please see the examples below.
-> No need to change existing provisioning settings.
+{{% admonition type="note" %}}
+`database` [field is deprecated](https://github.com/grafana/grafana/pull/58647).
+We suggest to use `dbName` field in `jsonData`. Please see the examples below.
+No need to change existing provisioning settings.
+{{% /admonition %}}

 #### Provisioning examples

@@ -53,8 +53,10 @@ You can also configure settings specific to the Jaeger data source. These option

 ![Trace to logs settings](/media/docs/tempo/tempo-trace-to-logs-9-4.png)

-> **Note:** Available in Grafana v7.4 and higher.
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+Available in Grafana v7.4 and higher.
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to logs** setting configures the [trace to logs feature]({{< relref "../../explore/trace-integration" >}}) that is available when you integrate Grafana with Jaeger.

@@ -110,8 +112,10 @@ The following table describes the ways in which you can configure your trace to

 ### Trace to metrics

-> **Note:** This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to metrics** setting configures the [trace to metrics feature](/blog/2022/08/18/new-in-grafana-9.1-trace-to-metrics-allows-users-to-navigate-from-a-trace-span-to-a-selected-data-source/) available when integrating Grafana with Jaeger.

@@ -295,8 +299,10 @@ If the file has multiple traces, Grafana visualizes its first trace.

 ## Span Filters

-> **Note:** This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 ![Screenshot of span filtering](/media/docs/tempo/screenshot-grafana-tempo-span-filters.png)

@@ -45,7 +45,9 @@ To configure basic settings for the data source, complete the following steps:
   | **Allowed cookies** | Defines which cookies are forwarded to the data source. Grafana Proxy deletes all other cookies.                                                                    |
   | **Maximum lines**   | Sets the upper limit for the number of log lines returned by Loki. Defaults to 1,000. Lower this limit if your browser is sluggish when displaying logs in Explore. |

-> **Note:** To troubleshoot configuration and other issues, check the log file located at `/var/log/grafana/grafana.log` on Unix systems, or in `<grafana_install_dir>/data/log` on other platforms and manual installations.
+{{% admonition type="note" %}}
+To troubleshoot configuration and other issues, check the log file located at `/var/log/grafana/grafana.log` on Unix systems, or in `<grafana_install_dir>/data/log` on other platforms and manual installations.
+{{% /admonition %}}

 ### Configure derived fields

@@ -57,7 +59,9 @@ The **Derived Fields** configuration helps you:
 For example, you can link to your tracing backend directly from your logs, or link to a user profile page if the log line contains a corresponding userId.
 These links appear in the [log details]({{< relref "../../explore/logs-integration/#labels-and-detected-fields" >}}).

-> **Note:** If you use Grafana Cloud, you can request modifications to this feature by [opening a support ticket in the Cloud Portal](/profile/org#support).
+{{% admonition type="note" %}}
+If you use Grafana Cloud, you can request modifications to this feature by [opening a support ticket in the Cloud Portal](/profile/org#support).
+{{% /admonition %}}

 Each derived field consists of:

@@ -30,7 +30,9 @@ To switch between the editor modes, select the corresponding **Builder** and **C

 To run a query, select **Run queries** located at the top of the editor.

-> **Note:** To run Loki queries in [Explore]({{< relref "../../../explore/" >}}), select **Run query**.
+{{% admonition type="note" %}}
+To run Loki queries in [Explore]({{< relref "../../../explore/" >}}), select **Run query**.
+{{% /admonition %}}

 Each mode is synchronized with the other modes, so you can switch between them without losing your work, although there are some limitations.

@@ -161,7 +163,9 @@ In your `server` section, add the following configuration:
  }
 ```

-> **Note:** Available in Grafana v6.3 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v6.3 and higher.
+{{% /admonition %}}

 ## Create a metric query

@@ -178,7 +178,9 @@ The response from MySQL can be formatted as either a table or as a time series.

 ### Dataset and Table selection

-> **Note:** If your table or database name contains a reserved word or a [not permitted character](https://dev.mysql.com/doc/refman/8.0/en/identifiers.html) the editor will put quotes around them. For example a table name like `table-name` will be quoted with backticks `` `table-name` ``.
+{{% admonition type="note" %}}
+If your table or database name contains a reserved word or a [not permitted character](https://dev.mysql.com/doc/refman/8.0/en/identifiers.html) the editor will put quotes around them. For example a table name like `table-name` will be quoted with backticks `` `table-name` ``.
+{{% /admonition %}}

 In the dataset dropdown, choose the MySQL database to query. The dropdown is be populated with the databases that the user has access to.
 When the dataset is selected, the table dropdown is populated with the tables that are available.
@@ -74,7 +74,9 @@ can be used to query opentsdb. Fill Policy is also introduced in OpenTSDB 2.2.

 ![](/static/img/docs/v43/opentsdb_query_editor.png)

-> **Note:** While using OpenTSDB 2.2 data source, make sure you use either Filters or Tags as they are mutually exclusive. If used together, might give you weird results.
+{{% admonition type="note" %}}
+While using OpenTSDB 2.2 data source, make sure you use either Filters or Tags as they are mutually exclusive. If used together, might give you weird results.
+{{% /admonition %}}

 ### Auto complete suggestions

@@ -149,7 +149,9 @@ datasources:
      timescaledb: false
 ```

-> **Note:** In the above code, the `postgresVersion` value of `10` refers to version PostgreSQL 10 and above.
+{{% admonition type="note" %}}
+In the above code, the `postgresVersion` value of `10` refers to version PostgreSQL 10 and above.
+{{% /admonition %}}

 #### Troubleshoot provisioning

@@ -135,7 +135,9 @@ For details on AWS SigV4, refer to the [AWS documentation](https://docs.aws.amaz

 #### AWS Signature Version 4 authentication

-> **Note:** Available in Grafana v7.3.5 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.3.5 and higher.
+{{% /admonition %}}

 To connect the Prometheus data source to Amazon Managed Service for Prometheus using SigV4 authentication, refer to the AWS guide to [Set up Grafana open source or Grafana Enterprise for use with AMP](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-query-standalone-grafana.html).

@@ -143,7 +145,9 @@ If you run Grafana in an Amazon EKS cluster, follow the AWS guide to [Query usin

 ### Configure exemplars

-> **Note:** Available in Prometheus v2.26 and higher with Grafana v7.4 and higher.
+{{% admonition type="note" %}}
+Available in Prometheus v2.26 and higher with Grafana v7.4 and higher.
+{{% /admonition %}}

 Grafana 7.4 and higher can show exemplars data alongside a metric both in Explore and in Dashboards.
 Exemplars associate higher-cardinality metadata from a specific event with traditional time series data.
@@ -87,8 +87,10 @@ The **Type** setting selects the query type.

 - An **Exemplars** query runs with the regular query and shows exemplars in the graph.

-> **Note:** Grafana modifies the request dates for queries to align them with the dynamically calculated step.
-> This ensures a consistent display of metrics data, but it can result in a small gap of data at the right edge of a graph.
+{{% admonition type="note" %}}
+Grafana modifies the request dates for queries to align them with the dynamically calculated step.
+This ensures a consistent display of metrics data, but it can result in a small gap of data at the right edge of a graph.
+{{% /admonition %}}

 ## Code mode

@@ -123,7 +125,9 @@ When you select a metric, the browser narrows down the available labels to show
 You can then select one or more labels for which the available label values are shown in lists in the bottom section.
 Select one or more values for each label to tighten your query scope.

-> **Note:** If you do not remember a metric name to start with, you can also select a few labels to narrow down the list, then find relevant label values.
+{{% admonition type="note" %}}
+If you do not remember a metric name to start with, you can also select a few labels to narrow down the list, then find relevant label values.
+{{% /admonition %}}

 All lists in the metrics browser have a search field above them to quickly filter for metrics or labels that match a certain string.
 The values section has only one search field, and its filtering applies to all labels to help you find values across labels once selected.
@@ -63,7 +63,9 @@ Regex:

 ## Use `$__rate_interval`

-> **Note:** Available in Grafana v7.2 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.2 and higher.
+{{% /admonition %}}

 We recommend using `$__rate_interval` in the `rate` and `increase` functions instead of `$__interval` or a fixed interval value.
 Because `$__rate_interval` is always at least four times the value of the Scrape interval, it avoid problems specific to Prometheus.
@@ -53,8 +53,10 @@ You can also configure settings specific to the Tempo data source. These options

 ![Trace to logs settings](/media/docs/tempo/tempo-trace-to-logs-9-4.png)

-> **Note:** Available in Grafana v7.4 and higher.
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+Available in Grafana v7.4 and higher.
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to logs** setting configures the [trace to logs feature]({{< relref "../../explore/trace-integration" >}}) that is available when you integrate Grafana with Tempo.

@@ -110,8 +112,10 @@ The following table describes the ways in which you can configure your trace to

 ### Trace to metrics

-> **Note:** This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to metrics** setting configures the [trace to metrics feature](/blog/2022/08/18/new-in-grafana-9.1-trace-to-metrics-allows-users-to-navigate-from-a-trace-span-to-a-selected-data-source/) available when integrating Grafana with Tempo.

@@ -350,8 +354,10 @@ To open the Service Graph view:
 1. Run the query.
 1. _(Optional)_ Filter your results.

-> **Note:** Grafana uses the `traces_spanmetrics_calls_total` metric to display the name, rate, and error rate columns, and `traces_spanmetrics_latency_bucket` to display the duration column.
-> These metrics must exist in your Prometheus data source.
+{{% admonition type="note" %}}
+Grafana uses the `traces_spanmetrics_calls_total` metric to display the name, rate, and error rate columns, and `traces_spanmetrics_latency_bucket` to display the duration column.
+These metrics must exist in your Prometheus data source.
+{{% /admonition %}}

 To open a query in Prometheus with the span name of that row automatically set in the query, click a row in the **rate**, **error rate**, or **duration** columns.

@@ -359,8 +365,10 @@ To open a query in Tempo with the span name of that row automatically set in the

 ## Span Filters

-> **Note:** This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 ![Screenshot of span filtering](/media/docs/tempo/screenshot-grafana-tempo-span-filters.png)

@@ -51,8 +51,10 @@ To configure basic settings for the data source, complete the following steps:

 ![Trace to logs settings](/media/docs/tempo/tempo-trace-to-logs-9-4.png)

-> **Note:** Available in Grafana v7.4 and higher.
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+Available in Grafana v7.4 and higher.
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to logs** setting configures the [trace to logs feature]({{< relref "../../explore/trace-integration" >}}) that is available when you integrate Grafana with Zipkin.

@@ -108,8 +110,10 @@ The following table describes the ways in which you can configure your trace to

 ### Trace to metrics

-> **Note:** This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `traceToMetrics` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 The **Trace to metrics** setting configures the [trace to metrics feature](/blog/2022/08/18/new-in-grafana-9.1-trace-to-metrics-allows-users-to-navigate-from-a-trace-span-to-a-selected-data-source/) available when integrating Grafana with Zipkin.

@@ -264,8 +268,10 @@ If the file has multiple traces, Grafana visualizes its first trace.

 ## Span Filters

-> **Note:** This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
-> If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% admonition type="note" %}}
+This feature is behind the `newTraceViewHeader` [feature toggle]({{< relref "../../setup-grafana/configure-grafana#feature_toggles" >}}).
+If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
+{{% /admonition %}}

 ![Screenshot of span filtering](/media/docs/tempo/screenshot-grafana-tempo-span-filters.png)