Appropiate Design Pattern to track metrics with Dropwizard

I am researching about Dropwizard Metrics + ElasticSearch as a Time Series Data Store. Even I have found easy to make it work at development stage, I wonder if there is a way to add (intrusive) Metrics code as the project grows while keeping it clean. Is there a commonly used Design Pattern when tracking metrics? I mean, an implementation that could let us mantain our code decoupled, business from metrics.

Thanks!