mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
23 lines
1.6 KiB
Plaintext
23 lines
1.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * monitoring/configuring-the-monitoring-stack.adoc
|
|
|
|
[id="support-considerations_{context}"]
|
|
= Support considerations for monitoring
|
|
|
|
The following modifications are explicitly not supported:
|
|
|
|
* *Creating additional ServiceMonitor, PodMonitor, and PrometheusRule objects in the `openshift-*`, and `kube-*` projects.*
|
|
* *Modifying any resources or objects deployed in the `openshift-monitoring` or `openshift-user-workload-monitoring` projects.* The resources created by the {product-title} monitoring stack are not meant to be used by any other resources, as there are no guarantees about their backward compatibility.
|
|
+
|
|
[NOTE]
|
|
====
|
|
The Alertmanager configuration is deployed as a secret resource in the `openshift-monitoring` project. To configure additional routes for Alertmanager, you need to decode, modify, and then encode that secret. This procedure is a supported exception to the preceding statement.
|
|
====
|
|
+
|
|
* *Modifying resources of the stack.* The {product-title} monitoring stack ensures its resources are always in the state it expects them to be. If they are modified, the stack will reset them.
|
|
* *Deploying user-defined workloads to `openshift-*`, and `kube-*` projects.* These projects are reserved for Red Hat provided components and they should not be used for user-defined workloads.
|
|
* *Modifying the monitoring stack Grafana instance.*
|
|
* *Installing custom Prometheus instances on {product-title}.*
|
|
* *Enabling symptom based monitoring by using the Probe Custom Resource Definition (CRD) in Prometheus Operator.*
|