Disabling Alerts on Kubernetes Resources

Last updated on 15 November, 2022

Kubernetes enables you to add identifying attributes in the form of key/value pairs to Kubernetes resources. Using Kubernetes labels, you can enable and disable alerts for a required resource or resource groups. For more information, see Labels and Selectors in the Kubernetes documentation.

Disabling Alerts on a Particular Resource

To disable alerts on a particular resource, you can add the following label to the resource specification:

argus.logicmonitor.com/alert=disable

You can also use the kubectl CLI to  add the  label to a resource as follows:

kubectl label <resource> argus.logicmonitor.com/alert=disable

Disabling Alerting on All Resources Within a Namespace

To disable alerts on namespaces, you can add the following label to the namespace specification:

argus.logicmonitor.com/alert=disable

Upon detecting the label, LM Container will stop raising alerts for any resource within the namespace.

Disabling Alerting on All Cluster-Scoped Resources

If you want to disable alerts on cluster-scoped resources in bulk, you can edit or add the following configuration settings in the Helm chart file.

Following is the example for disabling alert settings on cluster-scoped resources:

argus:
  lm:
    resource:
      alerting:
        disable: []
argus:
    lm:
 resource:
   alerting:
      disable:
nodes
persistentvolume

Note: Ensure to add only the cluster-scoped resources in the disabling alerts configuration settings. If you add the other namespaces-scoped resources, it might cause the LM Container services to malfunction.

In This Article