New to Searchlight? Please start here.


What is NodeAlert

A NodeAlert is a Kubernetes Custom Resource Definition (CRD). It provides declarative configuration of Icinga services for Nodes in a Kubernetes native way. You only need to describe the desired check command and notifier in a NodeAlert object, and the Searchlight operator will create Icinga2 hosts, services and notifications to the desired state for you.

NodeAlert Spec

As with all other Kubernetes objects, a NodeAlert needs apiVersion, kind, and metadata fields. It also needs a .spec section. Below is an example NodeAlert object.

kind: NodeAlert
  name: webstore
  namespace: demo
  selector: linux
  check: node-volume
    warning: '70'
    critical: '95'
  checkInterval: 5m
  alertInterval: 3m
  notifierSecretName: notifier-config
  - notifier: Mailgun
    state: Warning
    to: ["[email protected]"]
  - notifier: Twilio
    state: Critical
    to: ["+1-234-567-8901"]

This object will do the followings:

  • This Alert is set on nodes with matching label
  • Check command node-volume will be used.
  • Icinga will check for volume size every 5m.
  • Notifications will be sent every 3m if any problem is detected, until acknowledged.
  • When the disk is 70% full, it will reach Warning state and emails will be sent to [email protected] via Mailgun as notification.
  • When the disk is 95% full, it will reach Critical state and SMSes will be sent to +1-234-567-8901 via Twilio as notification.

Any NodeAlert object has 3 main sections:

Node Selection

Any NodeAlert can specify nodes in 2 ways:

  • spec.nodeName can be used to specify a node by name.

  • spec.selector is a node selector. Searchlight operator will update Icinga as nodes with matching labels are added/removed.

Check Command

Check commands are used by Icinga to periodically test some condition. If the test return positive appropriate notifications are sent. The following check commands are supported for nodes:

Each check command has a name specified in spec.check field. Optionally each check command can take one or more parameters. These are specified in spec.vars field. To learn about the available parameters for each check command, please visit their documentation. spec.checkInterval specifies how frequently Icinga will perform this check. Some examples are: 30s, 5m, 6h, etc.


When a check fails, Icinga will keep sending notifications until acknowledged via IcingaWeb dashboard. spec.alertInterval specifies how frequently notifications are sent. Icinga can send notifications to different targets based on alert state. spec.receivers contains that list of targets:

spec.receivers[*].stateRequired Name of state for which notification will be sent
spec.receivers[*].toRequired To whom notifications will be sent
spec.receivers[*].methodRequired How this notification will be sent

Icinga Objects

You can skip this section if you are unfamiliar with how Icinga works. Searchlight operator watches for NodeAlert objects and turns them into Icinga objects accordingly. For each Kubernetes Node which has an NodeAlert configured, an Icinga Host is created with the name {namespace}@node@{node-name} and address matching the internal IP of the Node. Now for each NodeAlert, an Icinga service is created with name matching the NodeAlert name.

Pause NodeAlert

You can pause a NodeAlert by setting spec.pause to true. If you already have a NodeAlert created, you can edit it to set spec.pause. Searchlight operator will delete all Icinga Services related to this NodeAlert. That’s how, periodical checks by Icinga will be stopped.

  pause: true

You can resume the process again by setting spec.pause to false. Then Searchlight operator will create Icinga Services again for this NodeAlert.

Next Steps

  • Visit the links below to learn about the available check commands for nodes:
  • To periodically run various checks on a Kubernetes cluster, use ClusterAlerts.
  • To periodically run various checks on pods in a Kubernetes cluster, use PodAlerts.
  • See the list of supported notifiers here.
  • Wondering what features are coming next? Please visit here.
  • Want to hack on Searchlight? Check our contribution guidelines.