|
7 | 7 | = Default monitoring targets
|
8 | 8 |
|
9 | 9 | ifndef::openshift-dedicated,openshift-rosa[]
|
10 |
| -In addition to the components of the stack itself, the default monitoring stack monitors: |
| 10 | +In addition to the components of the stack itself, the default monitoring stack monitors additional platform components. |
| 11 | + |
| 12 | +The following are examples of monitoring targets: |
11 | 13 | endif::openshift-dedicated,openshift-rosa[]
|
12 | 14 |
|
13 | 15 | ifdef::openshift-dedicated,openshift-rosa[]
|
14 |
| -Red Hat Site Reliability Engineers (SRE) monitor the following platform targets in your {product-title} cluster: |
| 16 | +The following are examples of targets monitored by Red{nbsp}Hat Site Reliability Engineers (SRE) in your {product-title} cluster: |
15 | 17 | endif::openshift-dedicated,openshift-rosa[]
|
16 | 18 |
|
17 | 19 | * CoreDNS
|
18 |
| -* Elasticsearch (if Logging is installed) |
19 | 20 | * etcd
|
20 |
| -* Fluentd (if Logging is installed) |
21 | 21 | * HAProxy
|
22 | 22 | * Image registry
|
23 | 23 | * Kubelets
|
24 | 24 | * Kubernetes API server
|
25 | 25 | * Kubernetes controller manager
|
26 | 26 | * Kubernetes scheduler
|
| 27 | +ifndef::openshift-rosa[] |
27 | 28 | * OpenShift API server
|
28 | 29 | * OpenShift Controller Manager
|
29 | 30 | * Operator Lifecycle Manager (OLM)
|
30 |
| -* Vector (if Logging is installed) |
| 31 | +endif::openshift-rosa[] |
| 32 | +
|
| 33 | +ifdef::openshift-dedicated,openshift-rosa[] |
| 34 | +[NOTE] |
| 35 | +==== |
| 36 | +The exact list of targets can vary depending on your cluster capabilities and installed components. |
| 37 | +==== |
| 38 | +endif::openshift-dedicated,openshift-rosa[] |
31 | 39 |
|
32 | 40 | ifndef::openshift-dedicated,openshift-rosa[]
|
33 | 41 | [NOTE]
|
34 | 42 | ====
|
35 |
| -Each {product-title} component is responsible for its monitoring configuration. For problems with the monitoring of an {product-title} component, open a |
| 43 | +* The exact list of targets can vary depending on your cluster capabilities and installed components. |
| 44 | +
|
| 45 | +* Each {product-title} component is responsible for its monitoring configuration. For problems with the monitoring of an {product-title} component, open a |
36 | 46 | link:https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332330&summary=Monitoring_issue&issuetype=1&priority=10200&versions=12385624[Jira issue] against that component, not against the general monitoring component.
|
37 | 47 | ====
|
38 | 48 |
|
|
0 commit comments