![](/img/trans.png)
[英]Dropwizard metrics annotations are not working in Spring Boot 1.5
[英]Dropwizard Metric Annotations @Timed not working
我正在嘗試使用@Timed( http://metrics.dropwizard.io/3.1.0/apidocs/com/codahale/metrics/annotation/package-summary.html )等注釋自動將指標發布到我的MetricRegistry。
這不是開箱即用的。 在搜索問題時,我發現了Codahale Metrics:在普通Java中使用@Timed指標注釋,其中提到了這個工作的唯一方法是使用aspectj。 我將此添加到我的項目中,但仍然沒有在MetricRegistry中看到我的指標。
這是我的pom文件。 我添加了一個librato庫,它在com.codahale.metrics:metrics-annotation
加載。
<dependency>
<groupId>io.astefanutti.metrics.aspectj</groupId>
<artifactId>metrics-aspectj</artifactId>
<version>${metrics-aspectj.version}</version>
</dependency>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>1.8.10</version>
</dependency>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>1.7</version>
<configuration>
<showWeaveInfo>true</showWeaveInfo>
<source>1.8</source>
<target>1.8</target>
<complianceLevel>1.8</complianceLevel>
<encoding>UTF-8</encoding>
<verbose>true</verbose>
<aspectLibraries>
<aspectLibrary>
<groupId>io.astefanutti.metrics.aspectj</groupId>
<artifactId>metrics-aspectj</artifactId>
</aspectLibrary>
</aspectLibraries>
</configuration>
<executions>
<execution>
<phase>process-sources</phase>
<goals>
<goal>compile</goal>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
</plugin>
<dependency>
<groupId>com.librato.metrics</groupId>
<artifactId>metrics-librato</artifactId>
<version>${metrics-librato.version}</version>
</dependency>
這就是我嘗試使用指標的方式
@Metrics(registry = "default") // this.metricRegistry is default
public class Foo {
@Inject
private MetricRegistry metricRegistry;
...
@Metered(name = "meterName")
public void bar() {
Meter meter = metricRegistry.meter("manual");
meter.mark();
// this.metricRegistry does not contain "meterName" after the ConsoleReporter prints the metrics for "default"
// this.metricRegistry contains "manual" after the ConsoleReporter prints the metrics for "default"
}
我在編譯時在日志中看到這個:
[INFO] Extending interface set for type 'Foo' (Foo.java) to include 'io.astefanutti.metrics.aspectj.Profiled' (MetricAspect.aj)
[INFO] Type 'Foo' (Foo.java) has intertyped field from 'io.astefanutti.metrics.aspectj.MetricAspect' (MetricAspect.aj:'java.util.Map<java.lang.String,io.astefanutti.metrics.aspectj.AnnotatedMetric<com.codahale.metrics.Gauge>> io.astefanutti.metrics.aspectj.Profiled.gauges')
[INFO] Type 'Foo' (Foo.java) has intertyped field from 'io.astefanutti.metrics.aspectj.MetricAspect' (MetricAspect.aj:'java.util.Map<java.lang.String,io.astefanutti.metrics.aspectj.AnnotatedMetric<com.codahale.metrics.Meter>> io.astefanutti.metrics.aspectj.Profiled.meters')
[INFO] Type 'Foo' (Foo.java) has intertyped field from 'io.astefanutti.metrics.aspectj.MetricAspect' (MetricAspect.aj:'java.util.Map<java.lang.String,io.astefanutti.metrics.aspectj.AnnotatedMetric<com.codahale.metrics.Timer>> io.astefanutti.metrics.aspectj.Profiled.timers')
[INFO] Join point 'staticinitialization(void Foo.<clinit>())' in Type 'Foo' (Foo.java:46) advised by after advice from 'io.astefanutti.metrics.aspectj.MetricStaticAspect' (metrics-aspectj-1.2.0.jar!MetricStaticAspect.class:41(from MetricStaticAspect.aj))
[INFO] Join point 'method-execution(void Foo.bar())' in Type 'Foo' (Foo.java:74) advised by around advice from 'io.astefanutti.metrics.aspectj.TimedAspect' (metrics-aspectj-1.2.0.jar!TimedAspect.class:26(from TimedAspect.aj))
[INFO] Join point 'method-execution(void Foo.bar())' in Type 'Foo' (Foo.java:74) advised by before advice from 'io.astefanutti.metrics.aspectj.MeteredAspect' (metrics-aspectj-1.2.0.jar!MeteredAspect.class:26(from MeteredAspect.aj))
它似乎表明我設置的注釋指標正常工作。 但是,我也在日志中也看到了這一點
[WARNING] advice defined in io.astefanutti.metrics.aspectj.TimedStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/TimedStaticAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.ExceptionMeteredAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/ExceptionMeteredAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.ExceptionMeteredStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/ExceptionMeteredStaticAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.MeteredStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/MeteredStaticAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.TimedAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/TimedAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.TimedStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/TimedStaticAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.MetricAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/MetricAspect.class:45
[WARNING] advice defined in io.astefanutti.metrics.aspectj.ExceptionMeteredAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/ExceptionMeteredAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.MeteredAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/MeteredAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.ExceptionMeteredStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/ExceptionMeteredStaticAspect.class:26
[WARNING] advice defined in io.astefanutti.metrics.aspectj.MetricStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/MetricStaticAspect.class:41
[WARNING] advice defined in io.astefanutti.metrics.aspectj.MeteredStaticAspect has not been applied [Xlint:adviceDidNotMatch]
/Users/x/.m2/repository/io/astefanutti/metrics/aspectj/metrics-aspectj/1.2.0/metrics-aspectj-1.2.0.jar!io/astefanutti/metrics/aspectj/MeteredStaticAspect.class:26
這是我的應用設置
@Override
public void run(AppConfiguration configuration, Environment environment) {
ConsoleReporter reporter = ConsoleReporter.forRegistry(environment.metrics())
.convertRatesTo(TimeUnit.SECONDS)
.convertDurationsTo(TimeUnit.MILLISECONDS)
.build();
reporter.start(2, TimeUnit.MINUTES);
}
我剛試了這個,效果很好。 這是我的整個設置:
pom.xml中:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>my-app</artifactId>
<packaging>jar</packaging>
<version>1.0-SNAPSHOT</version>
<name>my-app</name>
<url>http://maven.apache.org</url>
<dependencies>
<dependency>
<groupId>io.astefanutti.metrics.aspectj</groupId>
<artifactId>metrics-aspectj</artifactId>
<version>1.2.0</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<configuration>
<aspectLibraries>
<aspectLibrary>
<groupId>io.astefanutti.metrics.aspectj</groupId>
<artifactId>metrics-aspectj</artifactId>
</aspectLibrary>
</aspectLibraries>
<complianceLevel>1.8</complianceLevel>
<source>1.8</source>
<target>1.8</target>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.4.1</version>
<configuration>
<!-- get all project dependencies -->
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
<!-- MainClass in mainfest make a executable jar -->
<archive>
<manifest>
<mainClass>com.mkyong.core.utils.App</mainClass>
</manifest>
</archive>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<!-- bind to the packaging phase -->
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
請注意,我需要添加aspectj-maven-plugin
。 我還添加了一個assembly
插件,以便稍后進行測試。 這不是真的必要,我只是不想去尋找我本地盒子的依賴。
我的定時課:
package com.mycompany.app;
import java.util.concurrent.ThreadLocalRandom;
import com.codahale.metrics.annotation.Timed;
import io.astefanutti.metrics.aspectj.Metrics;
@Metrics(registry = "someMetrics")
public class TimedClass {
@Timed(name = "test")
public void doSomething() {
try {
Thread.sleep(200L);
} catch (InterruptedException e) {
}
System.out.println("Done");
}
@Timed(name = "test-random")
public void doSomething2() {
try {
Thread.sleep(ThreadLocalRandom.current().nextLong(100L));
} catch (InterruptedException e) {
}
System.out.println("Done");
}
}
和應用程序:
package com.mycompany.app;
import java.util.concurrent.TimeUnit;
import com.codahale.metrics.ConsoleReporter;
import com.codahale.metrics.MetricRegistry;
import com.codahale.metrics.SharedMetricRegistries;
public class App {
public static void main(String[] args) throws InterruptedException {
MetricRegistry metrics =
SharedMetricRegistries.getOrCreate("someMetrics");
ConsoleReporter.forRegistry(metrics)
.convertRatesTo(TimeUnit.SECONDS)
.convertDurationsTo(TimeUnit.MILLISECONDS)
.build()
.start(1, TimeUnit.SECONDS);
TimedClass c = new TimedClass();
for(int i = 0; i < 10; i++) {
c.doSomething();
c.doSomething2();
}
c.doSomething();
Thread.sleep(1010L);
}
}
這里發生的是,為方面編譯 maven插件時將找到您使用的注釋並應用方面。
在你的情況下(和我的)例如來自metrics-aspect源的這個:
final aspect TimedAspect {
pointcut timed(Profiled object) : execution(@Timed !static * (@Metrics Profiled+).*(..)) && this(object);
Object around(Profiled object) : timed(object) {
String methodSignature = ((MethodSignature) thisJoinPointStaticPart.getSignature()).getMethod().toString();
Timer timer = object.timers.get(methodSignature).getMetric();
Timer.Context context = timer.time();
try {
return proceed(object);
} finally {
context.stop();
}
}
}
以上所做的就是說:
任何非靜態且具有@Timed
注釋的方法都應在“around”方法中執行。
現在,您可以通過執行以下操作來編譯和打包:
mvn clean install package
這將為非應用方面打印一堆警告,但這非常好(我們實際上並沒有使用它們)。
此外,你現在有一個包含你的應用程序的胖罐,你可以執行它來看看我們做了什么:
java -cp target/my-app-1.0-SNAPSHOT-jar-with-dependencies.jar com.mycompany.app.App
哪個會打印:
artur@pdb-ct ~/dev/repo/my-app $ java -cp target/my-app-1.0-SNAPSHOT-jar-with-dependencies.jar com.mycompany.app.App
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Done
Done
Done
Done
Done
Done
Done
Done
04/01/18 15:10:42 ==============================================================
-- Timers ----------------------------------------------------------------------
com.mycompany.app.TimedClass.test
count = 4
mean rate = 4.11 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 200.21 milliseconds
max = 200.37 milliseconds
mean = 200.29 milliseconds
stddev = 0.06 milliseconds
median = 200.25 milliseconds
75% <= 200.32 milliseconds
95% <= 200.37 milliseconds
98% <= 200.37 milliseconds
99% <= 200.37 milliseconds
99.9% <= 200.37 milliseconds
com.mycompany.app.TimedClass.test-random
count = 4
mean rate = 4.10 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 20.41 milliseconds
max = 32.28 milliseconds
mean = 26.07 milliseconds
stddev = 4.56 milliseconds
median = 28.26 milliseconds
75% <= 32.28 milliseconds
95% <= 32.28 milliseconds
98% <= 32.28 milliseconds
99% <= 32.28 milliseconds
99.9% <= 32.28 milliseconds
Done
Done
Done
Done
Done
Done
Done
04/01/18 15:10:43 ==============================================================
-- Timers ----------------------------------------------------------------------
com.mycompany.app.TimedClass.test
count = 8
mean rate = 4.06 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 200.16 milliseconds
max = 200.37 milliseconds
mean = 200.25 milliseconds
stddev = 0.06 milliseconds
median = 200.25 milliseconds
75% <= 200.26 milliseconds
95% <= 200.37 milliseconds
98% <= 200.37 milliseconds
99% <= 200.37 milliseconds
99.9% <= 200.37 milliseconds
com.mycompany.app.TimedClass.test-random
count = 7
mean rate = 3.55 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 20.41 milliseconds
max = 97.20 milliseconds
mean = 43.68 milliseconds
stddev = 28.17 milliseconds
median = 28.26 milliseconds
75% <= 76.30 milliseconds
95% <= 97.20 milliseconds
98% <= 97.20 milliseconds
99% <= 97.20 milliseconds
99.9% <= 97.20 milliseconds
Done
Done
Done
Done
Done
Done
04/01/18 15:10:44 ==============================================================
-- Timers ----------------------------------------------------------------------
com.mycompany.app.TimedClass.test
count = 11
mean rate = 3.70 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 200.13 milliseconds
max = 200.37 milliseconds
mean = 200.23 milliseconds
stddev = 0.07 milliseconds
median = 200.21 milliseconds
75% <= 200.26 milliseconds
95% <= 200.37 milliseconds
98% <= 200.37 milliseconds
99% <= 200.37 milliseconds
99.9% <= 200.37 milliseconds
com.mycompany.app.TimedClass.test-random
count = 10
mean rate = 3.37 calls/second
1-minute rate = 0.00 calls/second
5-minute rate = 0.00 calls/second
15-minute rate = 0.00 calls/second
min = 15.19 milliseconds
max = 97.20 milliseconds
mean = 48.90 milliseconds
stddev = 30.99 milliseconds
median = 32.28 milliseconds
75% <= 76.30 milliseconds
95% <= 97.20 milliseconds
98% <= 97.20 milliseconds
99% <= 97.20 milliseconds
99.9% <= 97.20 milliseconds
幾點:
這並不在Eclipse中工作。 你必須安裝一個擴展才能使它工作(我還沒試過),請看這里:
https://github.com/astefanutti/metrics-aspectj/blob/master/README.md
有關如何使用AJDT的說明:
https://www.ibm.com/developerworks/library/j-ajdt/
原因是(模糊,因為我沒有花太多時間在這上面),方面是在編譯時應用的,而不是在運行時。 Eclipse在IDE中運行時使用自己的編譯器,因此它只執行您的代碼。 然后,您的pom文件中的maven插件在編譯代碼時應用了這些方面。
我希望有幫助,
PS原諒我的命名/包裝 - 我使用了默認的maven生成器
- 阿圖爾
跟進:
要添加dropwizard指標,如果要使用上述解決方案,只需將其添加到共享指標即可。 例如:
MetricRegistry myCustomRegistry = new MetricRegistry();
SharedMetricRegistries.add("my-metric-registry", myCustomRegistry);
在您的情況下,這將來自environment().metrics()
或類似。
您遇到的問題是AspectJ建議使用的MetricRegistry
實例與您用於手動計量測試和ConsoleReporter
的實例不同。
由於您的問題未指定@Inject
-ed MetricRegistry
實例的來源,我只能推測它與您使用ConsoleReporter
實例相同,但這很可能是與"default"
注冊表使用的實例不同的實例。 AspectJ的建議 。 AspectJ建議使用的是
SharedMetricRegistries.getOrCreate("default");
為了解決您的問題,您應該 :
確保@Inject
-ed MetricRegistry
實例和environment.metrics()
返回的實例與SharedMetricRegistries.getOrCreate("default")
,使用您首選的依賴注入框架使用工廠方法的方式( @Bean
for Spring , @Produces
為CDI)。
在Foo
類@Metrics
注釋的registry
值中使用EL表達式,如下所示:
@Metrics(registry = "${this.metricRegistry}")
為metricRegistry
屬性提供一個getter:
public MetricRegistry getMetricRegistry() { return this.metricRegistry; }
並確保您在項目中擁有所需的EL庫:
<dependency> <groupId>org.glassfish</groupId> <artifactId>javax.el</artifactId> <version>3.0.1-b09</version> </dependency>
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.