4.5.3. Understanding Insights Operator alerts
The Insights Operator declares alerts through the Prometheus monitoring system to the Alertmanager. You can view these alerts in the Alerting UI in the OpenShift Container Platform web console by using one of the following methods:
-
In the Administrator perspective, click Observe
Alerting. -
In the Developer perspective, click Observe
<project_name> Alerts tab.
Currently, Insights Operator sends the following alerts when the conditions are met:
| Alert | Description |
|---|---|
|
| Insights Operator is disabled. |
|
| Simple content access is not enabled in Red Hat Subscription Management. |
|
| Red Hat Lightspeed has an active recommendation for the cluster. |
4.5.3.1. Disabling Insights Operator alerts 링크 복사링크가 클립보드에 복사되었습니다!
To prevent the Insights Operator from sending alerts to the cluster Prometheus instance, you create or edit the insights-config ConfigMap object.
Previously, a cluster administrator would create or edit the Insights Operator configuration using a support secret in the openshift-config namespace. Red Hat Lightspeed now supports the creation of a ConfigMap object to configure the Operator. The Operator gives preference to the config map configuration over the support secret if both exist.
If the insights-config ConfigMap object does not exist, you must create it when you first add custom configurations. Note that configurations within the ConfigMap object take precedence over the default settings defined in the config/pod.yaml file.
Prerequisites
- Remote health reporting is enabled, which is the default.
-
You are logged in to the OpenShift Container Platform web console as
cluster-admin. -
The insights-config
ConfigMapobject exists in theopenshift-insightsnamespace.
Procedure
-
Go to Workloads
ConfigMaps and select Project: openshift-insights. -
Click on the insights-config
ConfigMapobject to open it. - Click Actions and select Edit ConfigMap.
- Click the YAML view radio button.
In the file, set the
alertingattribute todisabled: true.apiVersion: v1 kind: ConfigMap # ... data: config.yaml: | alerting: disabled: true # ...- Click Save. The insights-config config-map details page opens.
Verify that the value of the
config.yamlalertingattribute is set todisabled: true.After you save the changes, Insights Operator no longer sends alerts to the cluster Prometheus instance.