Event monitoring is a monitoring method provided by Kubernetes. It provides improvements over the resource monitoring in terms of timeliness, accuracy, and scenarios. Developers can diagnose cluster anomalies based on the events that are collected in real time.
Background information
Kubernetes is designed based on state machines. Events are generated due to transitions between different states. Typically, Normal events are generated when state machines change to expected states, and Warning events are generated when state machines change to unexpected states. kube-eventer is an open source event emitter that is maintained by Container Service for Kubernetes (ACK). kube-eventer sends Kubernetes events to sinks such as DingTalk and Log Service. kube-eventer also provides filter conditions to filter different levels of events. You can use kube-eventer to collect events in real time, trigger alerts upon specific events, and asynchronously archive events. For more information, see kube-eventer.
This topic describes how to configure event monitoring in the following scenarios:
Scenario 1: Use DingTalk to raise alerts upon Kubernetes events
Using a DingTalk chatbot to monitor Kubernetes events and raise alerts is a typical scenario of ChatOps. Perform the following steps to configure a DingTalk chatbot to raise alerts:

Scenario 2: Sink Kubernetes events to Log Service
You can sink Kubernetes events to Log Service for persistent storage, and archive and audit these events. For more information, see Create and use a Kubernetes event center.
Scenario 3: Use node-problem-detector with kube-eventer to raise alerts upon node anomalies
node-problem-detector is a tool to diagnose Kubernetes nodes. node-problem-detector detects node anomalies, generates node events, and works with kube-eventer to raise alerts upon these events. node-problem-detector generates node events when the following anomalies are detected: Docker engine hangs, Linux kernel hangs, outbound traffic anomalies, and file descriptor anomalies. Perform the following steps to raise alerts upon node events:
Scenario 4: Use node-problem-detector with the Kubernetes event center of Log Service to sink cluster events
node-problem-detector works with the preceding plug-ins to detect node anomalies and generate cluster events. A Kubernetes cluster also generates events when the status of the cluster changes. For example, when a pod is evicted or an image pull fails, a related event is generated. The Kubernetes event center of Log Service collects, stores, and visualizes cluster events. It allows you to query and analyze these events, and configure alerts. To sink cluster events to the Kubernetes event center in the Log Service console, adopt the following methods:
Method 1: If Install node-problem-detector and Create Event Center was selected when you created the cluster, perform the following steps to go to the Kubernetes event center. For more information about how to install node-problem-detector and deploy the Kubernetes event center when you create a cluster, see Create a managed Kubernetes cluster.
Method 2: If the Kubernetes event center was not deployed when you created the cluster, perform the following steps to deploy and use the Kubernetes event center.