I'm trying to track object server GET errors using statsd and I'm not seeing them. The test I'm doing is to simply do a GET on an non-existent object. As expected, a 404 is returned and the object server log records it. However, statsd implies it succeeded because there were no errors reported. A read of the admin guide does clearly say the GET timing includes failed GETs, but my question then becomes how is one to tell there was a failure? Should there be another type of message that DOES report errors? Or how about including these in the 'object-server.GET.errors.timing' message?
Since the server I'm testing on is running all services, you get to see them together, but if I was looking at a standalone object server I'd never know: account-server.HEAD.timing:1.85513496399|ms proxy-server.account.HEAD.204.timing:21.3139057159|ms proxy-server.account.HEAD.204.xfer:0|c proxy-server.container.HEAD.204.timing:6.98900222778|ms proxy-server.container.HEAD.204.xfer:0|c account-server.HEAD.timing:1.72400474548|ms proxy-server.account.HEAD.204.timing:19.4480419159|ms proxy-server.account.HEAD.204.xfer:0|c object-server.GET.timing:0.359058380127|ms object-server.GET.timing:0.255107879639|ms proxy-server.object.GET.404.first-byte.timing:7.84802436829|ms proxy-server.object.GET.404.timing:8.13698768616|ms proxy-server.object.GET.404.xfer:70|c -mark
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
