In general, you're right. It's pretty important to know what's going on in the cluster. However, the checks for these background daemons shouldn't be done in the wsgi servers. Generally, we've stayed away from a lot of process monitoring in the Swift core. That it, Swift already works around failures, and there is already existing ops tooling to monitor if a process is alive.
Check out the swift-recon tool that's included with Swift. It already includes some checks like the replication cycle time. While it's not a direct "is this process alive" monitoring tool, it does give good information about the health of the cluster. If you've got some other ideas on checks to add to recon or ways to make it better or perhaps even some different ways to integrate monitoring systems, let us know! --John On Jul 7, 2014, at 7:33 PM, Osanai, Hisashi <osanai.hisa...@jp.fujitsu.com> wrote: > > Hi, > > Current Healthcheck middleware provides the functionality of monitoring > Servers such as > Proxy Server, Object Server, Container Server, Container Server and Account > Server. The > middleware checks whether each Servers can handle request/response. > My idea to enhance this middleware is > checking daemons such replications, updaters and auditors existence in > addition to current one. > If we realize this, the scope of Health would be extended from > "a Server can handle request" to "a Server and daemons can work > appropriately". > > http://docs.openstack.org/developer/swift/icehouse/middleware.html?highlight=health#healthcheck > > What do you think? > > Best Regards, > Hisashi Osanai > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
