Package org.eclipse.microprofile.metrics
Rational
To ensure reliable operation of software it is necessary to monitor essential system parameters. There is already JMX as standard to expose metrics, but remote-JMX is not easy to deal with and especially does not fit well in a polyglot environment where other services are not running on the JVM. To enable monitoring in an easy fashion, the MicroProfile Metrics specification provides a standard to instrument an application with metrics and provides a simple REST endpoint for integration with monitoring services.
Adding Metrics
MicroProfile Metrics provides 6 different metric types that can be used to instrument an application. Developers can
create an accompanying Metadata object to supply the metric's name,
description, display name, and units. Once the metric and the metadata are registered against the application
MetricRegistry, the metrics will be available in the REST
endpoints.
Metric Types
Counter is used to measure an increasing value.
Example usage:
Counter count = metricRegistry.counter(metadata);
count.inc();
ConcurrentGauge is used to monitor the number of concurrent
invocations of a component.
Example usage:
ConcurrentGauge cgauge = metricRegistry.concurrentGauge(metadata);
cgauge.inc();
// .. a block of code that can be executed by multiple threads at the same time
cgauge.dec();
Gauge is used to provide the immediate measurement of a value.
Example usage:
Gauge<Double> temperature = new Gauge<Double>() {
public Double getValue() {
return getTemperature();
}
};
metricRegistry.register(metadata, temperature);
Meter is used to measure the frequency of an event.
Example usage:
Meter meter = metricRegistry.meter(metadata);
meter.mark();
Histogram is used to sample and compute the distribution of values
Example usage:
Histogram histogram = metricRegistry.histogram(metadata);
histogram.update(score);
Timer is used to measure the duration of an event as well as the
frequency of occurrence.
Example usage:
Timer timer = metricRegistry.timer(metadata);
Timer.Context context = timer.time();
... // code that will be timed
context.close();
SimpleTimer is used to measure the duration of an event.
Example usage:
SimpleTimer simpleTimer = metricRegistry.simpleTimer(metadata);
SimpleTimer.Context context = simpleTimer.time();
... // code that will be timed
context.close();
-
ClassDescriptionA concurrent gauge is a gauge that measures parallel invocations of a method.An incrementing counter metric.An interface for metric types which have counts.The default implementation of
MetadataGauge<T>A gauge metric is an instantaneous reading of a particular value.A metric which calculates the distribution of a value.Bean holding the metadata of one single metric.TheMetadatabuilder.A meter metric which measures mean throughput and one-, five-, and fifteen-minute exponentially-weighted moving average throughputs.An object which maintains mean and exponentially-weighted rate.A tag interface to indicate that a class is a metric.A filter used to determine whether or not a metric should be reported, among other things.A unique identifier forMetricandMetadatathat are registered in theMetricRegistryThe MetricID contains:Name: (Required) The name of the metric.Tags: (Optional) The tags (represented byTagobjects) of the metric.The registry that stores metrics and their metadata.An enumeration representing the scopes of the MetricRegistryAn enumeration representing the different types of metrics.Standard units constants for metric'sMetadata.An object which samples values.A simple timer metric which tracks elapsed time durations and count.A timing context.A statistical snapshot of aSnapshot.Tag represents a singular metric tag key and value pair.A timer metric which aggregates timing durations and provides duration statistics, plus throughput statistics viaMeter.A timing context.