mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Update sig monitoring doc
This commit is contained in:
parent
2d736d30b1
commit
480c73fed3
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## Overview
|
||||
|
||||
The KubeSphere monitoring system comprises many components that work together to achieve overall monitoring functionality. KubeSphere defaults to installing the monitoring module. It will deploy or create a few components within the namespace `kubesphere-monitoring-system`:
|
||||
The KubeSphere monitoring system comprises of many components that work together to achieve overall monitoring functionality. KubeSphere defaults to installing the monitoring module. It will deploy or create a few components within the namespace `kubesphere-monitoring-system`:
|
||||
|
||||
- Prometheus Operator: automates tasks for operating Prometheus instances.
|
||||
- Prometheus: scrapes metrics and provides monitoring service.
|
||||
|
|
@ -15,7 +15,7 @@ Besides, the monitoring stack includes CRD resources:
|
|||
- Prometheus: defines a desired Prometheus deployment.
|
||||
- PrometheusRule: defines a desired Prometheus rule file.
|
||||
|
||||
In KubeSphere, Prometheus will monitor the following services by default:
|
||||
In KubeSphere, Prometheus will monitor the following services by default:
|
||||
|
||||
- kube-state-metrics
|
||||
- node-exporter
|
||||
|
|
@ -33,4 +33,4 @@ The [contrib/kube-prometheus](https://github.com/kubesphere/prometheus-operator/
|
|||
|
||||
The diagram below presents the overall monitoring architecture:
|
||||
|
||||

|
||||

|
||||
|
|
|
|||
Loading…
Reference in New Issue