Probably one of the worst design choices a metrics library developer can make is supporting a reset like operation. Whilst it is well understood why a developer (with limited operational experience) might request such capabilities it should be avoided as it not only adds to the development effort of measures (i.e. concurrent state management) that form the basis of metrics it invariably complicates the development of plugins and console clients especially with regard to cumulative measurements which are now no longer guaranteed to be cumulative in value. It also raises concern around security.

Measurement data is collected at a cost and holds value though admittedly it does deprecate once removed from its space and time context. In our opinion it should never be possible to wipe the slate clean for even a single metric – at least not for base metric measures....

http://www.jinspired.com/site/how-not-to-design-a-metrics-api-part-5-alternatives-to-reset