The event messages we saw in the output of kubectl describe contain valuable information and complement the metrics gathered by kube-state-metrics. This allows us to determine exactly what happened to our pods or nodes. Consequently, those event messages should be part of our logging essentials, together with system and application logs. In order to achieve this, we'll need something to watch Kubernetes API servers and aggregate events into a logging sink. The event objects inside Kubernetes are also stored in etcd, but tapping into the storage to get those event objects might require a lot of work. Projects such as eventrouter (https://github.com/heptiolabs/eventrouter) can help in this scenario. Eventrouter works by translating event objects to structured messages and emitting them to its stdout. As a result, our logging system can treat those events as normal logs while keeping the metadata of events.