canonicized monitoring-v2-configuration (#851)

rancher · Sep 18, 2023 · 08f6c59 · 08f6c59
1 parent aa12232
commit 08f6c59
Show file tree

Hide file tree

Showing 20 changed files with 80 additions and 0 deletions.
diff --git a/docs/reference-guides/monitoring-v2-configuration/examples.md b/docs/reference-guides/monitoring-v2-configuration/examples.md
@@ -2,6 +2,10 @@
 title: Examples
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/examples"/>
+</head>
+
 ### ServiceMonitor
 
 An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)

diff --git a/docs/reference-guides/monitoring-v2-configuration/helm-chart-options.md b/docs/reference-guides/monitoring-v2-configuration/helm-chart-options.md
@@ -2,6 +2,10 @@
 title: Helm Chart Options
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/helm-chart-options"/>
+</head>
+
 ## Configuring Resource Limits and Requests
 
 The resource requests and limits can be configured when installing `rancher-monitoring`.

diff --git a/docs/reference-guides/monitoring-v2-configuration/receivers.md b/docs/reference-guides/monitoring-v2-configuration/receivers.md
@@ -2,6 +2,10 @@
 title: Receiver Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/receivers"/>
+</head>
+
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
 :::note

diff --git a/docs/reference-guides/monitoring-v2-configuration/routes.md b/docs/reference-guides/monitoring-v2-configuration/routes.md
@@ -2,6 +2,10 @@
 title: Route Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/routes"/>
+</head>
+
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.
 
 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.

diff --git a/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md b/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md
@@ -2,6 +2,10 @@
 title: ServiceMonitor and PodMonitor Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors"/>
+</head>
+
 ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource.
 
 These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from.

diff --git a/...ioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/examples.md b/...ioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/examples.md
@@ -2,6 +2,10 @@
 title: Examples
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/examples"/>
+</head>
+
 ### ServiceMonitor
 
 An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)

diff --git a/.../version-2.5/reference-guides/monitoring-v2-configuration/helm-chart-options.md b/.../version-2.5/reference-guides/monitoring-v2-configuration/helm-chart-options.md
@@ -2,6 +2,10 @@
 title: Helm Chart Options
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/helm-chart-options"/>
+</head>
+
 ## Configuring Resource Limits and Requests
 
 The resource requests and limits can be configured when installing `rancher-monitoring`.

diff --git a/...oned_docs/version-2.5/reference-guides/monitoring-v2-configuration/receivers.md b/...oned_docs/version-2.5/reference-guides/monitoring-v2-configuration/receivers.md
@@ -2,6 +2,10 @@
 title: Receiver Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/receivers"/>
+</head>
+
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
 > This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md#3-how-alertmanager-works)

diff --git a/versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/routes.md b/versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/routes.md
@@ -2,6 +2,10 @@
 title: Route Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/routes"/>
+</head>
+
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.
 
 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.

diff --git a/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md b/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md
@@ -2,6 +2,10 @@
 title: ServiceMonitor and PodMonitor Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors"/>
+</head>
+
 ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource.
 
 These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from.

diff --git a/...ioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/examples.md b/...ioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/examples.md
@@ -2,6 +2,10 @@
 title: Examples
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/examples"/>
+</head>
+
 ### ServiceMonitor
 
 An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)

diff --git a/.../version-2.6/reference-guides/monitoring-v2-configuration/helm-chart-options.md b/.../version-2.6/reference-guides/monitoring-v2-configuration/helm-chart-options.md
@@ -2,6 +2,10 @@
 title: Helm Chart Options
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/helm-chart-options"/>
+</head>
+
 ## Configuring Resource Limits and Requests
 
 The resource requests and limits can be configured when installing `rancher-monitoring`.

diff --git a/...oned_docs/version-2.6/reference-guides/monitoring-v2-configuration/receivers.md b/...oned_docs/version-2.6/reference-guides/monitoring-v2-configuration/receivers.md
@@ -2,6 +2,10 @@
 title: Receiver Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/receivers"/>
+</head>
+
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
 :::note

diff --git a/versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/routes.md b/versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/routes.md
@@ -2,6 +2,10 @@
 title: Route Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/routes"/>
+</head>
+
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.
 
 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.

diff --git a/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md b/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md
@@ -2,6 +2,10 @@
 title: ServiceMonitor and PodMonitor Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors"/>
+</head>
+
 ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource.
 
 These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from.

diff --git a/...ioned_docs/version-2.7/reference-guides/monitoring-v2-configuration/examples.md b/...ioned_docs/version-2.7/reference-guides/monitoring-v2-configuration/examples.md
@@ -2,6 +2,10 @@
 title: Examples
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/examples"/>
+</head>
+
 ### ServiceMonitor
 
 An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)

diff --git a/.../version-2.7/reference-guides/monitoring-v2-configuration/helm-chart-options.md b/.../version-2.7/reference-guides/monitoring-v2-configuration/helm-chart-options.md
@@ -2,6 +2,10 @@
 title: Helm Chart Options
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/helm-chart-options"/>
+</head>
+
 ## Configuring Resource Limits and Requests
 
 The resource requests and limits can be configured when installing `rancher-monitoring`.

diff --git a/...oned_docs/version-2.7/reference-guides/monitoring-v2-configuration/receivers.md b/...oned_docs/version-2.7/reference-guides/monitoring-v2-configuration/receivers.md
@@ -2,6 +2,10 @@
 title: Receiver Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/receivers"/>
+</head>
+
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
 :::note

diff --git a/versioned_docs/version-2.7/reference-guides/monitoring-v2-configuration/routes.md b/versioned_docs/version-2.7/reference-guides/monitoring-v2-configuration/routes.md
@@ -2,6 +2,10 @@
 title: Route Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/routes"/>
+</head>
+
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.
 
 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.

diff --git a/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md b/...reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md
@@ -2,6 +2,10 @@
 title: ServiceMonitor and PodMonitor Configuration
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com//reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors"/>
+</head>
+
 ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource.
 
 These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from.