Fix all the old usage of admonition syntax (#107017)

docs/sources/datasources/prometheus/_index.md

@@ -82,14 +82,14 @@ refs:
 
 Prometheus is an open source database that uses a telemetry collector agent to scrape and store metrics used for monitoring and alerting. Grafana provides native support for Prometheus. If you are just getting started with Prometheus, see [What is Prometheus?](ref:intro-to-prometheus).
 
-{{% admonition type="tip" %}}
+{{< admonition type="tip" >}}
 For instructions on downloading Prometheus see [Get started with Grafana and Prometheus](ref:get-started-prometheus).
 
 If you’re ready to start visualizing your metrics, check out our Prometheus Learning Journeys:
 
 - [Connect to a Prometheus data source in Grafana Cloud](https://www.grafana.com/docs/learning-journeys/prometheus/) to visualize your metrics directly from where they are stored.
 - [Send metrics to Grafana Cloud using Prometheus remote write](https://www.grafana.com/docs/learning-journeys/prom-remote-write/) to explore Grafana Cloud without making significant changes to your existing configuration.
-  {{% /admonition %}}
+  {{< /admonition >}}
 
 For instructions on how to add a data source to Grafana, refer to the [administration documentation](ref:administration-documentation).
 Only users with the organization `administrator` role can add data sources and edit existing data sources.
@@ -117,9 +117,9 @@ For more information on how to query other Prometheus-compatible projects from G
 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](ref:provisioning-data-sources).
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 Once you have provisioned a data source you cannot edit it.
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Provisioning example
 
@@ -183,17 +183,17 @@ Add the following setting in the **[auth]** section :
 azure_auth_enabled = true
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 If you are using Azure authentication settings do not enable `Forward OAuth identity`. Both use the same HTTP authorization headers. Azure settings will get overwritten by the Oauth token.
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Exemplars
 
 Exemplars associate higher-cardinality metadata from a specific event with traditional time series data. See [Introduction to exemplars](ref:exemplars) in Prometheus documentation for detailed information on how they work.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 Available in Prometheus v2.26 and higher with Grafana v7.4 and higher.
-{{% /admonition %}}
+{{< /admonition >}}
 
 Grafana can show exemplars data alongside a metric both in Explore and in Dashboards.
 

docs/sources/datasources/prometheus/configure-prometheus-data-source.md

@@ -92,11 +92,11 @@ You should use the IP address of the Prometheus container, or the hostname if yo
 
 There are several authentication methods you can choose in the Authentication section.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Use TLS (Transport Layer Security) for an additional layer of security when working with Prometheus. For information on setting up TLS encryption with Prometheus see [Securing Prometheus API and UI Endpoints Using TLS Encryption](https://prometheus.io/docs/guides/tls-encryption/). You must add TLS settings to your Prometheus configuration file **prior** to setting these options in Grafana.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 - **Basic authentication** - The most common authentication method. Use your `data source` user name and `data source` password to connect.
 
@@ -130,11 +130,11 @@ Following are additional configuration options.
 
 - **Manage alerts via Alerting UI** - Toggle to enable [data source-managed rules in Grafana Alerting](ref:alerting-alert-rules) for this data source. For `Mimir`, it enables managing data source-managed rules and alerts. For `Prometheus`, it only supports viewing existing rules and alerts, which are displayed as data source-managed.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 The **Manage alerts via Alerting UI** toggle is enabled by default. You can change this behavior by setting the [default_manage_alerts_ui_toggle](../../../setup-grafana/configure-grafana/#default_manage_alerts_ui_toggle) option in the Grafana configuration file.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Interval behavior
 

docs/sources/datasources/prometheus/query-editor/index.md

@@ -120,18 +120,18 @@ The **Type** setting sets the query type. These include:
 
 For more information, refer to the [Time Series Transform option documentation](ref:time-series-transform).
 
-{{% admonition type="note" %}}
+{{< 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 and Prometheus requires this for caching results. But, aligning the range with the step can result in a small gap of data at the right edge of a graph or change the start date of the range. For example, a 15s step aligns the range to Unix time divisible by 15s and a 1w minstep aligns the range to the start of the week on a Thursday.
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Exemplars
 
 Toggle **Exemplars** to run a query that includes exemplars in the graph. Exemplars are unique to Prometheus. For more information see [Introduction to exemplars](ref:exemplars).
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 There is no option to add exemplars with an **Instant** query type.
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Inspector
 
@@ -243,9 +243,9 @@ You can then select one or more labels shown in Step 2.
 Select one or more values in Step 3 for each label to tighten your query scope.
 In Step 4, you can select **Use query** to run the query, **Use as rate query** to add the rate operation to your query (`$__rate_interval`), **Validate selector** to verify the selector is valid and show the number of series found, or **Clear** to clear your selections and start over.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 If you do not remember a metric name, you can also select a few labels to narrow down the list, then find relevant label values.
-{{% /admonition %}}
+{{< /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.