Hi Raj,

We can use the same CEP stream to publish cartridge agent health stats. We
can identify the instance type (container or VM type) by retrieving member
properties from the topology. But I don't think we should be doing that.

IMO, we should not publish cartridge agent health stats from each and every
container. It's better if we can have a global agent per Kubernetes host
instance to monitor the health of every container and also in host instance
itself. We can use a container monitoring agent like cAdvisor to collect
container health stats.

+1 for having a separate CEP execution plan for handling Docker containers
scenario.

As for the ContainerClusterMonitor, we should clearly outline the
responsibilities of container monitor and VM monitor. Because since we are
using Kubernetes for managing the life-cycle of containers, most of the
tasks are already taken care of. For eg - we don't need to start a new
container if an existing containers fails since Kubernetes will handle that
failure.

WDYT?

Reply via email to