You can explicitly name timers (or all metrics for that matter).  For dynamic names you'd have to code the timer as you can't really do this from the @Timed annotation IIUC.


On September 17, 2013 at 11:35:48 AM, Tamas Cservenak (notifications@github.com) wrote:

In components/nexus-core/src/main/java/org/sonatype/nexus/proxy/storage/remote/httpclient/HttpClientRemoteStorage.java:

>      try {
>        return doExecuteRequest(repository, request, httpRequest);
>      }
>      finally {
>        if (stopwatch != null) {
>          stopwatch.stop();
> -        if (timingLog.isDebugEnabled()) {
> -          timingLog.debug("[{}] {} {} took {}", repository.getId(), httpRequest.getMethod(),
> -              httpRequest.getURI(), stopwatch);
> -        }
> +        timingLog.debug("[{}] {} {} took {}", repository.getId(), httpRequest.getMethod(), httpRequest.getURI(),
> +            stopwatch);
Ok, will use then MatricsRegistry + Timer then here. Still, I hold this logger as very useful, as this is not about timing, but more about ease of debugging for outgoing HTTP RRS traffic.

Is Yammer able to time per-URL or keyed by something?

—
Reply to this email directly or view it on GitHub.