Configuration Rules for Kubernetes

Configuration Rules enable you to associate predefined actions for different monitor groups to track configuration changes and maintain optimal settings. These rules allow for specific criteria to be established, which determines the actions that will be applied to the monitors. 

Set up Configuration Rules

Supported OS platforms: Linux

1. Log in to Site24x7 and go to Admin > Inventory > Configuration Rules.
2. Click Add Rule.
3. Enter a Display Name and Description for the rule.
4. Stop Executing Other Rules: Select Yes to skip all the remaining rules once this rule is applied to a monitor. 
5. In the Define Criteria section, choose how the conditions are combined:
   1. Any of these Conditions (OR): The rule applies when at least one condition is met.
   2. All of these conditions (AND): The rule applies when all conditions are met. This option is selected by default. 
6. Set the Criteria. Select Type > is > Kubernetes. Click the plus icon + to add more conditions.
7. In the Define Actions section, use the drop-down menu and associate the following actions for Kubernetes:
   • Threshold Profile: Select a threshold profile to apply to the matching monitors.
   • Notification Profile: Select a notification profile to apply to the matching monitors.
   • Monitor Group: Add the matching monitors to one or more monitor groups. Select Append to add or Replace to overwrite the existing monitor group associations.
   • Third-Party Services: Associate third-party services for alert notifications. Select Append to add or Replace to overwrite the existing third-party service associations.
   • User Alert Group: Associate user alert groups to the specific set of users. Select Append to add or Replace to overwrite the existing user alert group associations with the selected groups. 

The other available options are listed below:

• Check Frequency: Set the poll interval to five minutes for data collection.
• Tags: Associate tags for the particular monitor to organize and manage monitors creatively.
• Dependent on Monitor: Select a dependency monitor for the matching monitors to depend on. Alerts for the matching monitors are suppressed when the selected monitor's status is Down. Select Append to add or Replace to overwrite the existing dependencies.
• On-Call Schedule: Ensure that the notifications are sent to assignees in specific shift hours to help them quickly respond to alerts or incidents.
• Enable Kubernetes Change Tracker: Select True, to enable the matching monitors to track configuration changes in your cluster.
• Mute Resource Termination Alerts: Set this to True if you don't want to receive alerts when the containers are suspended/deleted from Site24x7.
• Automatically Remove Terminated Resources: Set this to True if you want to remove terminated resources of Kubernetes from Site24x7.
• Add Resource Types: Select one or more resource type that you wish to monitor.

For each filter, select Include to add only resources that matches the provided RegEx or Exclude to skip resources that matches the provided RegEx. The available filters are listed below:

• • Filter Resources on Namespaces
  • Filter Resources on Name
  • Filter Resources on Labels
  • Filter Nodes for Addition Based on Name
  • Filter Pods for Addition Based on Name
  • Filter Containers for Addition Based on Name
  • Filter Services for Addition Based on Name
  • Filter DaemonSets for Addition Based on Name
  • Filter Deployments for Addition Based on Name
  • Filter HPAs for Addition Based on Name
  • Filter ReplicaSets for Addition Based on Name
  • Filter Endpoints for Addition Based on Name
  • Filter Replication Controllers for Addition Based on Name
  • Filter StatefulSets for Addition Based on Name
  • Filter Persistent Volume Claims for Addition Based on Name
  • Filter ConfigMaps for Addition Based on Name
  • Filter Persistent Volumes for Addition Based on Name
  • Filter Ingresses for Addition Based on Name
  • Filter API Server for Addition Based on Name
  • Filter Controller Manager for Addition Based on Name
  • Filter Kube-Proxy for Addition Based on Name
  • Filter etcd for Addition Based on Name
  • Filter CoreDNS for Addition Based on Name
  • Filter Kubelet for Addition Based on Name
  • Filter Scheduler for Addition Based on Name
    
    Note

    You can use RegEx to filter any type of resource and add them for monitoring. A sample is shown below: 
    mysql-.*|redis-.*|memcached-.* 
    This will match all the MySQL, Redis, and Memcached pods that align with the above pattern and add them for monitoring.

8. Select the type of automation you would like to execute from the IT Automation Templates and provide the necessary parameters to remediate routine actions automatically.
9. Click Save or Save and Run Rule to run the rule immediately. 

You can also select these monitor types in step six and follow the remaining steps as described above. 

1. Kubernetes Node:
2. • Disable node alerts: Set this to True if you don't want to receive alerts for the Kubernetes node.
2. Kubernetes Pod:
   • Disable pod alerts: Set this to True if you don't want to receive alerts for the Kubernetes pod.

Related articles

• Kubernetes monitoring
• Kubernetes performance metrics
• IT automation