public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove figcaption that has no associated image

Browse Source
This commit is contained in:
Billy Tat
2024-11-22 10:58:26 -08:00
parent 0b1a9b0d35
commit 8bf8fef3ba
13 changed files with 0 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data
versioned_docs/version-2.5/explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data
versioned_docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data
versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data
versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data
versioned_docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded
- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.).
<figcaption>How data flows through the monitoring application:</figcaption>
## 2. How Prometheus Works
### Storing Time Series Data