Metrics的基本介紹能夠參考以前的文章:Metrics-服務指標度量。java
本文簡單介紹下如何將Metrics監控集成到咱們的項目中。spring
本文所使用的metrics-core爲3.1.0版本。bash
<dependency>
<groupId>io.dropwizard.metrics</groupId>
<artifactId>metrics-core</artifactId>
<version>3.1.0</version>
</dependency>
複製代碼
咱們的主要的監控需求有如下方面:jvm
內存、線程、硬盤、服務GC狀況等基本信息是咱們關心的核心指標。咱們能夠考慮經過Gauge指標項把這些機器指標作統一收集。ide
請求頻率及耗時是咱們服務接口性能的核心指標,咱們能夠考慮經過Timer指標項來採集相關信息。post
在某些場景下咱們將內部Service統計到的瞬時指標上報,如Web Filter裏面統計當前正在處理的請求數等。咱們也可使用Gauge指標項來收集。性能
針對於以上場景,咱們雖然能夠經過寫代碼的方式建立和註冊相應的服務指標,但是在使用上卻不太友好。如何更方便靈活地將Metrics指標統計集成到咱們的項目中呢?this
指標集合MetricSet可參看metrics-jvm庫的MemoryUsageGaugeSet來定義,MemoryUsageGaugeSet定義了內存使用狀況的基本指標,以下所示。spa
/** * A set of gauges for JVM memory usage, including stats on heap vs. non-heap memory, plus * GC-specific memory pools. */
public class MemoryUsageGaugeSet implements MetricSet {
private static final Pattern WHITESPACE = Pattern.compile("[\\s]+");
private final MemoryMXBean mxBean;
private final List<MemoryPoolMXBean> memoryPools;
public MemoryUsageGaugeSet() {
this(ManagementFactory.getMemoryMXBean(),
ManagementFactory.getMemoryPoolMXBeans());
}
public MemoryUsageGaugeSet(MemoryMXBean mxBean, Collection<MemoryPoolMXBean> memoryPools) {
this.mxBean = mxBean;
this.memoryPools = new ArrayList<MemoryPoolMXBean>(memoryPools);
}
@Override
public Map<String, Metric> getMetrics() {
final Map<String, Metric> gauges = new HashMap<String, Metric>();
gauges.put("total.init", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getInit() +
mxBean.getNonHeapMemoryUsage().getInit();
}
});
gauges.put("total.used", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getUsed() +
mxBean.getNonHeapMemoryUsage().getUsed();
}
});
gauges.put("total.max", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getMax() +
mxBean.getNonHeapMemoryUsage().getMax();
}
});
gauges.put("total.committed", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getCommitted() +
mxBean.getNonHeapMemoryUsage().getCommitted();
}
});
gauges.put("heap.init", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getInit();
}
});
gauges.put("heap.used", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getUsed();
}
});
gauges.put("heap.max", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getMax();
}
});
gauges.put("heap.committed", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getHeapMemoryUsage().getCommitted();
}
});
gauges.put("heap.usage", new RatioGauge() {
@Override
protected Ratio getRatio() {
final MemoryUsage usage = mxBean.getHeapMemoryUsage();
return Ratio.of(usage.getUsed(), usage.getMax());
}
});
gauges.put("non-heap.init", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getNonHeapMemoryUsage().getInit();
}
});
gauges.put("non-heap.used", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getNonHeapMemoryUsage().getUsed();
}
});
gauges.put("non-heap.max", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getNonHeapMemoryUsage().getMax();
}
});
gauges.put("non-heap.committed", new Gauge<Long>() {
@Override
public Long getValue() {
return mxBean.getNonHeapMemoryUsage().getCommitted();
}
});
gauges.put("non-heap.usage", new RatioGauge() {
@Override
protected Ratio getRatio() {
final MemoryUsage usage = mxBean.getNonHeapMemoryUsage();
return Ratio.of(usage.getUsed(), usage.getMax());
}
});
for (final MemoryPoolMXBean pool : memoryPools) {
gauges.put(name("pools",
WHITESPACE.matcher(pool.getName()).replaceAll("-"),
"usage"),
new RatioGauge() {
@Override
protected Ratio getRatio() {
final long max = pool.getUsage().getMax() == -1 ?
pool.getUsage().getCommitted() :
pool.getUsage().getMax();
return Ratio.of(pool.getUsage().getUsed(), max);
}
});
}
return Collections.unmodifiableMap(gauges);
}
}
複製代碼
public class UserDefinedMetricBeanPostProcessor implements BeanPostProcessor {
private final Logger LOG = LoggerFactory.getLogger(getClass());
private final MetricRegistry metrics = MetricBeans.getRegistry();
@Override
public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
return bean;
}
@Override
public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
if (bean instanceof MetricSet) {
MetricSet metricSet = (MetricSet) bean;
if (!canRegister(beanName)) {
return bean;
}
String metricName;
if (isJvmCollector(beanName)) {
metricName = Config.getProjectPrefix() + "." + beanName;
} else {
//根據規則生成Metric的名字
metricName = Util.forMetricBean(bean.getClass(), beanName);
}
try {
metrics.register(metricName, metricSet);
LOG.debug("Registered metric named {} in registry. class: {}.", metricName, metricSet);
} catch (IllegalArgumentException ex) {
LOG.warn("Error injecting metric for field. bean named {}.", metricName, ex);
}
}
return bean;
}
private boolean isJvmCollector(String beanName) {
return beanName.indexOf("jvm") != -1;
}
private boolean canRegister(String beanName) {
return !isJvmCollector(beanName) || Config.canJvmCollectorStart();
}
}
複製代碼
<!--定義Jvm監控對象-->
<bean id="jvm.memory" class="com.codahale.metrics.jvm.MemoryUsageGaugeSet"/>
<!--自動添加用戶定義的監控對象Metric-->
<bean class="com.test.metrics.collector.UserDefinedMetricBeanPostProcessor"/>
複製代碼
能夠根據須要定製MetricSet集合,實現服務指標的自動註冊及上報。線程
咱們能夠結合註解實現成員變量的自動註冊。在BeanPostProcessor能夠獲取到成員變量的註解,如果咱們的目標註解,能夠經過反射的方式獲取到變量信息進行自動註冊。
下面以Gauged註解爲例說明,Gauged註解可讓成員變量自動註冊並上報。
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.METHOD, ElementType.FIELD, ElementType.ANNOTATION_TYPE })
public @interface Gauged {
String name() default "";
}
複製代碼
核心代碼以下所示:
protected void withField(final Object bean, String beanName, Class<?> targetClass, final Field field) {
ReflectionUtils.makeAccessible(field);
final Gauged annotation = field.getAnnotation(Gauged.class);
final String metricName = Util.forGauge(targetClass, field, annotation);
metrics.register(metricName, new Gauge<Object>() {
@Override
public Object getValue() {
return ReflectionUtils.getField(field, bean);
}
});
LOG.debug("Created gauge {} for field {}.{}", metricName, targetClass.getCanonicalName(), field.getName());
}
複製代碼
基本使用以下:
@Component
public class GaugeUsage {
@Gauged(name = "gaugeField")
private int gaugedField = 999;
}
複製代碼
基於Spring AOP能夠實現接口調用的耗時統計。
下面以Timed註解爲例,Timed註解能夠統計接口方法耗時狀況。
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.TYPE, ElementType.CONSTRUCTOR, ElementType.METHOD, ElementType.ANNOTATION_TYPE })
public @interface Timed {
String name() default "";
}
複製代碼
@Component
@Aspect
public class MetricAspect {
@Around("@annotation(timed)")
public Object processTimerAnnotation(ProceedingJoinPoint joinPoint, Timed timed) throws Throwable {
Class clazz = joinPoint.getTarget().getClass();
Method method = ((MethodSignature) joinPoint.getSignature()).getMethod();
String metricName = Util.forTimedMethod(clazz, method, timed);
Timer timer = MetricBeans.timer(metricName);
final Timer.Context context = timer.time();
try {
return joinPoint.proceed();
} finally {
context.stop();
}
}
}
複製代碼
基本示例以下:
@Component
public class TimedUsage {
//@Timed註解會讓監控組件建立Timer對象,統計該方法的執行次數和執行時間等指標
@Timed(name = "simple-timed-method")
public void timedMethod() {
for (int i = 0; i < 1000; i++) {
}
}
}
複製代碼
當前咱們主要經過BenPostProcessor和Spring AOP對類實例進行攔截,從而實現服務指標的自動註冊和收集。