I ran into this a while ago too. Unfortunately, the resource instrumentation afforded by the metrics library is downstream (i.e. later in the request lifecycle) than the Jetty handler which deals with gzip serialization. AFAICT there isn't an out-of-the-box means of measuring request latency including [de]serialization.
It would be pretty straightforward to have Dropwizard's BiDiGzipHandler emit measurements of request-handling latency from its perspective. This could be made configurable via a new option under server.gzip <http://www.dropwizard.io/1.0.0/docs/manual/configuration.html#gzip>. Happy to put together a PR if others think this could be useful. On Mon, Aug 1, 2016 at 5:44 PM, Alex Yakushev < [email protected]> wrote: > Hi, > > We're using @Timed annotations for metrics, which work great, except they > don't seem to include serialization. Is it possible to time the entire > request, not just the resource portion of it? > > Thanks, > > Alex > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Evan Meagher -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
