// Module included in the following assemblies:
//
// * support/remote_health_monitoring/using-insights-operator.adoc


:_mod-docs-content-type: PROCEDURE
[id="disabling-insights-operator-alerts_{context}"]
= Disabling {insights-operator} alerts

[role="_abstract"]
To prevent the {insights-operator} from sending alerts to the cluster Prometheus instance, you create or edit the `insights-config` `ConfigMap` object. 

ifndef::openshift-rosa,openshift-dedicated[]
[NOTE]
====
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.
endif::openshift-rosa,openshift-dedicated[]

.Prerequisites

* Remote health reporting is enabled, which is the default.
ifndef::openshift-rosa,openshift-dedicated[]
* You are logged in to the {product-title} web console as `cluster-admin`.
endif::openshift-rosa,openshift-dedicated[]
ifdef::openshift-rosa,openshift-dedicated[]
* You are logged in to the {product-title} web console as a user with the `dedicated-admin` role.
endif::openshift-rosa,openshift-dedicated[]
* The `insights-config` `ConfigMap` object exists in the `openshift-insights` namespace.

.Procedure

. Go to *Workloads* -> *ConfigMaps* and select *Project: openshift-insights*.

. Click the *insights-config* `ConfigMap` object to open it.

. Click *Actions* and select *Edit ConfigMap*.

. Click the *YAML view* radio button.

. In the file, set the `alerting` attribute to `disabled: true`.
+
[source,yaml]
----
apiVersion: v1
kind: ConfigMap
# ...
data:
  config.yaml: |
    alerting:
      disabled: true
# ...
----

. Click *Save*. The `insights-config` ConfigMap details page opens.

. Verify that the value of the `config.yaml` `alerting` attribute is set to `disabled: true`.
+
After you save the changes, {insights-operator} no longer sends alerts to the cluster Prometheus instance.
