This project is an implementation of the Vert.x Metrics Service Provider Interface (SPI). It uses Micrometer for managing metrics and reporting to several backends.
-
Vert.x core tools monitoring: TCP/HTTP client and servers, {@link io.vertx.core.datagram.DatagramSocket} , {@link io.vertx.core.eventbus.EventBus} and pools
-
User defined metrics through Micrometer
-
Reporting to any backend supported by Micrometer
-
Built-in options for InfluxDB, Prometheus and JMX reporting.
Follow the instructions to get InfluxDb up and running.
The modules vertx-micrometer-metrics and micrometer-registry-influx must be present in the classpath.
Maven users should add this to their project POM file:
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-micrometer-metrics</artifactId>
<version>${maven.version}</version>
</dependency>
<dependency>
<groupId>io.micrometer</groupId>
<artifactId>micrometer-registry-influx</artifactId>
<version>${micrometer.version}</version>
</dependency>
And Gradle users, to their build file:
compile 'io.vertx:vertx-micrometer-metrics:${maven.version}'
compile 'io.micrometer:micrometer-registry-influx:${micrometer.version}'
Vert.x does not enable SPI implementations by default. You must enable metric collection in the Vert.x options.
{@link examples.MicrometerMetricsExamples#setupMinimalInfluxDB()}
{@link examples.MicrometerMetricsExamples#setupInfluxDBWithUriAndDatabase()}
Follow the instructions to get Prometheus up and running.
The modules vertx-micrometer-metrics and micrometer-registry-prometheus must be present in the classpath. You may also probably need vertx-web, to expose the metrics.
Maven users should add this to their project POM file:
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-micrometer-metrics</artifactId>
<version>${maven.version}</version>
</dependency>
<dependency>
<groupId>io.micrometer</groupId>
<artifactId>micrometer-registry-prometheus</artifactId>
<version>${micrometer.version}</version>
</dependency>
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-web</artifactId>
<version>${maven.version}</version>
</dependency>
And Gradle users, to their build file:
compile 'io.vertx:vertx-micrometer-metrics:${maven.version}'
compile 'io.micrometer:micrometer-registry-prometheus:${micrometer.version}'
compile 'io.vertx:vertx-web:${maven.version}'
Vert.x does not enable SPI implementations by default. You must enable metric collection in the Vert.x options
{@link examples.MicrometerMetricsExamples#setupMinimalPrometheus()}
{@link examples.MicrometerMetricsExamples#setupPrometheusEmbeddedServer()}
If the embedded server endpoint is not specified, it defaults to /metrics.
The modules vertx-micrometer-metrics and micrometer-registry-jmx must be present in the classpath.
Maven users should add this to their project POM file:
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-micrometer-metrics</artifactId>
<version>${maven.version}</version>
</dependency>
<dependency>
<groupId>io.micrometer</groupId>
<artifactId>micrometer-registry-jmx</artifactId>
<version>${micrometer.version}</version>
</dependency>
And Gradle users, to their build file:
compile 'io.vertx:vertx-micrometer-metrics:${maven.version}'
compile 'io.micrometer:micrometer-registry-jmx:${micrometer.version}'
Vert.x does not enable SPI implementations by default. You must enable metric collection in the Vert.x options
{@link examples.MicrometerMetricsExamples#setupMinimalJMX()}
Even if not all backends supported by Micrometer are implemented in Vert.x options, it is still possible to create any Micrometer registry and pass it to Vert.x.
The list of available backends includes Graphite, Ganglia, Atlas, etc. It also enables the Micrometer Composite Registry in order to report the same metrics to multiple backends.
In this example, metrics are reported both for JMX and Graphite:
{@link examples.MicrometerMetricsExamples#setupWithCompositeRegistry()}
Please refer to {@link io.vertx.micrometer.MicrometerMetricsOptions} for an exhaustive list of options.
Restricting the Vert.x modules being monitored can be done using {@link io.vertx.micrometer.MicrometerMetricsOptions#disabledMetricsCategories}.
For a full list of domains, see {@link io.vertx.micrometer.MetricsDomain}
The Micrometer registries are accessible, in order to create new metrics or fetch the existing ones. By default, an unique registry is used and will be shared across the Vert.x instances of the JVM:
{@link examples.MicrometerMetricsExamples#accessDefaultRegistry()}
It is also possible to have separate registries per Vertx instance, by giving a registry name in metrics options. Then it can be retrieved specifically:
{@link examples.MicrometerMetricsExamples#setupAndAccessCustomRegistry()}
As an example, here is a custom timer that will track the execution time of a piece of code that is regularly called:
{@link examples.MicrometerMetricsExamples#customTimerExample()}
For more examples, documentation about the Micrometer registry and how to create metrics, check Micrometer doc.
Since plain access to Micrometer registries is provided, it is possible to leverage the Micrometer API. For instance, to instrument the JVM:
{@link examples.MicrometerMetricsExamples#instrumentJVM()}
From Micrometer documentation.
Vert.x Micrometer Metrics defines a set of labels (aka tags or fields) that are used to provide dimensionality to a metric. For instance, metrics related to event bus messages have an address label, which allows then to query timeseries for a specific event bus address, or compare timeseries per address, or perform any kind of aggregation that the query API allows.
While setting up metrics options, you can specify which labels you want to enable or not:
{@link examples.MicrometerMetricsExamples#setupWithLabelsEnabled()}
The full list of labels is detailed here: {@link io.vertx.micrometer.Label}.
Enabling labels may result in a high cardinality in values, which can cause troubles on the metrics backend and affect performances. So it must be used with care. In general, it is fine to enable labels when the set of possible values is bounded.
For that reason, labels enabled by default are restricted to the ones with known bounded values.
It is possible to interact with labels further than just enabling/disabling. There are two ways for that:
{@link io.vertx.micrometer.Match} objects can be used to filter or rename some label value by matching it with either an exact string or a regular expression (the former being more efficient).
Here is an example to restrict HTTP server metrics to those with label local=localhost:8080 only:
{@link examples.MicrometerMetricsExamples#setupWithMatcherForFiltering()}
When an alias is specified in the Match, it will be used to rename value instead of filtering.
Matchers are especially useful to control labelling through configuration as they are set via {@link io.vertx.micrometer.MicrometerMetricsOptions}.
Micrometer’s MeterFilter API can be accessed directly in order to define rules on labels. Compared to Matchers, it offers more features in manipulating the labels, but cannot be defined from configuration. So both have their advantages.
Here is an example to replace the actual path
label of HTTP requests with a generic form using regex:
{@link examples.MicrometerMetricsExamples#useMicrometerFilters()}
Note that Matchers use MeterFilters under the hood.
A {@link io.vertx.micrometer.MetricsService} can be created out of a {@link io.vertx.core.metrics.Measured} object in order to take a snapshot of its related metrics and measurements. The snapshot is returned as a {@link io.vertx.core.json.JsonObject}.
A well known Measured object is simply {@link io.vertx.core.Vertx}:
{@link examples.MicrometerMetricsExamples#createFullSnapshot()}
Other components, such as an {@link io.vertx.core.eventbus.EventBus} or a {@link io.vertx.core.http.HttpServer} are measurable:
{@link examples.MicrometerMetricsExamples#createPartialSnapshot()}
Finally it is possible to filter the returned metrics from their base names:
{@link examples.MicrometerMetricsExamples#createSnapshotFromPrefix()}
This section lists all the metrics generated by monitoring the Vert.x core tools.
Metric type | Metric name | Description |
---|---|---|
Gauge |
|
Number of connections to the remote host currently opened. |
Summary |
|
Number of bytes received from the remote host. |
Summary |
|
Number of bytes sent to the remote host. |
Counter |
|
Number of errors. |
Metric type | Metric name | Description |
---|---|---|
Gauge |
|
Number of connections to the remote host currently opened. |
Summary |
|
Number of bytes received from the remote host. |
Summary |
|
Number of bytes sent to the remote host. |
Counter |
|
Number of errors. |
Gauge |
|
Number of requests waiting for a response. |
Counter |
|
Number of requests sent. |
Timer |
|
Response time. |
Counter |
|
Number of received responses. |
Gauge |
|
Number of websockets currently opened. |
Metric type | Metric name | Description |
---|---|---|
Summary |
|
Total number of bytes received on the |
Summary |
|
Total number of bytes sent to the remote host. |
Counter |
|
Total number of errors. |
Metric type | Metric name | Description |
---|---|---|
Gauge |
|
Number of opened connections to the Net Server. |
Summary |
|
Number of bytes received by the Net Server. |
Summary |
|
Number of bytes sent by the Net Server. |
Counter |
|
Number of errors. |
Metric type | Metric name | Description |
---|---|---|
Gauge |
|
Number of opened connections to the HTTP Server. |
Summary |
|
Number of bytes received by the HTTP Server. |
Summary |
|
Number of bytes sent by the HTTP Server. |
Counter |
|
Number of errors. |
Gauge |
|
Number of requests being processed. |
Counter |
|
Number of processed requests. |
Counter |
|
Number of requests reset. |
Timer |
|
Request processing time. |
Gauge |
|
Number of websockets currently opened. |
Metric type | Metric name | Description |
---|---|---|
Gauge |
|
Number of event bus handlers in use. |
Counter |
|
Number of errors. |
Summary |
|
Total number of bytes sent while sending messages to event bus cluster peers. |
Summary |
|
Total number of bytes received while reading messages from event bus cluster peers. |
Gauge |
|
Number of messages not processed yet. One message published will count for |
Counter |
|
Number of messages published (publish / subscribe). |
Counter |
|
Number of messages sent (point-to-point). |
Counter |
|
Number of messages received. |
Counter |
|
Number of messages delivered to handlers. |
Counter |
|
Number of message reply failures. |
Timer |
|
Processing time for handlers listening to the |
This section lists all the metrics generated by monitoring Vert.x pools.
There are two types currently supported:
-
worker (see {@link io.vertx.core.WorkerExecutor})
-
datasource (created with Vert.x JDBC client)
Note
|
Vert.x creates two worker pools upfront, worker-thread and internal-blocking. |
Metric type | Metric name | Description |
---|---|---|
Timer |
|
Time waiting for a resource (queue time). |
Gauge |
|
Number of elements waiting for a resource. |
Timer |
|
Time using a resource (i.e. processing time for worker pools). |
Gauge |
|
Number of resources used. |
Counter |
|
Number of elements done with the resource (i.e. total number of tasks executed for worker pools). |
Gauge |
|
Pool usage ratio, only present if maximum pool size could be determined. |