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

2025-06-24 09:23:29 +01:00
parent 623302d055
commit ff2ac27301
142 changed files with 543 additions and 543 deletions
@@ -25,9 +25,9 @@ A label matchers consists of 3 distinct parts, the **label**, the **value** and
  | `=~`     | Select labels that regex-match the value.          |
  | `!~`     | Select labels that do not regex-match the value.   |

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 If you are using multiple label matchers, they are combined using the AND logical operator. This means that all matchers must match in order to link a rule to a policy.
-{{% /admonition %}}
+{{< /admonition >}}

 **Label matching example**

@@ -165,9 +165,9 @@ This works because both `.Alerts` and `.Alerts.Firing` is a list of alerts.
 {{ end }}
 ```

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 You cannot create independent, reusable templates for labels and annotations as you can with notification templates. In alert rule templates, you need to write each template inline within the label or annotation field.
-{{% /admonition %}}
+{{< /admonition >}}

 ## Comments

@@ -2,7 +2,7 @@
 title: 'Warning Provisioning Tree'
 ---

-{{% admonition type="warning" %}}
+{{< admonition type="warning" >}}

 Since the policy tree is a single resource, provisioning it will overwrite all policies in the notification policy tree. However, it does not affect internal policies created when alert rules directly select a contact point.

@@ -22,10 +22,10 @@ The Grafana configuration files are located in the following directories:

 For more information on where to find configuration files, refer to [Configuration file location](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/setup-grafana/configure-grafana/#configuration-file-location).

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 If you installed Grafana using the `deb` or `rpm` packages, then your configuration file is located at
 `/etc/grafana/grafana.ini`. This path is specified in the Grafana `init.d` script using `--config` file parameter.
-{{% /admonition %}}
+{{< /admonition >}}

 ## Back up plugin data

@@ -44,9 +44,9 @@ We recommend that you back up your Grafana database so that you can roll back to

 The default Grafana database is SQLite, which stores its data in a single file on disk. To back up this file, copy it to your backup repository.

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 To ensure data integrity, shut down your Grafana service before backing up the SQLite database.
-{{% /admonition %}}
+{{< /admonition >}}

 The SQLite database file is located in one of the following directories:

@@ -104,10 +104,10 @@ To add a tag, follow these steps:

 ### Optional: Use Aggregate by

-{{% admonition type="warning" %}}
+{{< admonition type="warning" >}}
 Metrics summary API and the **Aggregate by** feature are deprecated in Grafana Cloud and Grafana 11.3 and later.
 It will be removed in a future release.
-{{% /admonition %}}
+{{< /admonition >}}

 Using **Aggregate by**, you can calculate RED metrics (total span count, percent erroring spans, and latency information) for spans of `kind=server` that match your filter criteria, grouped by one or more attributes.
 This capability is based on the [metrics summary API](/docs/grafana-cloud/monitor-infrastructure/traces/metrics-summary-api/).
@@ -12,14 +12,14 @@ Because Grafana upgrades are backward compatible, the upgrade process is straigh

 In addition to common tasks you should complete for all versions of Grafana, there might be additional upgrade tasks to complete for a version.

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 There might be breaking changes in some releases. We outline these changes in the [What's New ](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/whatsnew/) document for most releases or a separate [Breaking changes](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/breaking-changes/) document for releases with many breaking changes.
-{{% /admonition %}}
+{{< /admonition >}}

 For versions of Grafana prior to v9.2, we published additional information in the [Release Notes](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/release-notes/).

 When available, we list all changes with links to pull requests or issues in the [Changelog](https://github.com/grafana/grafana/blob/main/CHANGELOG.md).

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 When possible, we recommend that you test the Grafana upgrade process in a test or development environment.
-{{% /admonition %}}
+{{< /admonition >}}
@@ -12,14 +12,14 @@ Because Grafana upgrades are backward compatible, the upgrade process is straigh

 In addition to common tasks you should complete for all versions of Grafana, there might be additional upgrade tasks to complete for a version.

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 There might be breaking changes in some releases. We outline all these changes in the [What's New](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/whatsnew/) document.
-{{% /admonition %}}
+{{< /admonition >}}

 For versions of Grafana prior to v9.2, we published additional information in the [Release Notes](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/release-notes/).

 When available, we list all changes with links to pull requests or issues in the [Changelog](https://github.com/grafana/grafana/blob/main/CHANGELOG.md).

-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 When possible, we recommend that you test the Grafana upgrade process in a test or development environment.
-{{% /admonition %}}
+{{< /admonition >}}
@@ -90,9 +90,9 @@ To upgrade Grafana running in a Docker container, complete the following steps:

 1. Run a commands similar to the following commands.

-   {{% admonition type="note" %}}
+   {{< admonition type="note" >}}
   This is an example. The parameters you enter depend on how you configured your Grafana container.
-   {{% /admonition %}}
+   {{< /admonition >}}

   ```bash
   docker pull grafana/grafana