Skip to content

@donbourne donbourne released this Jun 19, 2019 · 7 commits to master since this release

This is an update to MicroProfile Metrics 2.0.0, primarily to update the TCK to use a newer version of restassured, which enables the TCK to be run with JDK 11.

To use this release, pull in

<dependency>
    <groupId>org.eclipse.microprofile.metrics</groupId>
    <artifactId>microprofile-metrics-api</artifactId>
    <version>2.0.1</version>
</dependency>

There are no functional changes since tag 2.0.0

Assets 4

@jmartisk jmartisk released this Jun 20, 2019 · 161 commits to master since this release

This is a minor update over 1.1.1.

To use this release, pull in

<dependency>
    <groupId>org.eclipse.microprofile.metrics</groupId>
    <artifactId>microprofile-metrics-api</artifactId>
    <version>1.1.2</version>
</dependency>

The changes are mostly new test coverage and test fixes in the TCKs. Also the values of global tags are now being correctly retrieved using MP Config, in accordance with the specification text.

Assets 2
Jun 18, 2019
[maven-release-plugin] copy for tag 2.0.1-RC1
Jun 12, 2019
[maven-release-plugin] copy for tag 1.1.2-RC1

@pilhuhn pilhuhn released this May 23, 2019 · 17 commits to master since this release

This is a re-spin of MicroProfile Metric 2.0 with a small improvement in Javadoc and a version of OSGi tooling that is the one of the Metrics 2.0 RCs.

To use this release, pull in

<dependency>
    <groupId>org.eclipse.microprofile.metrics</groupId>
    <artifactId>microprofile-metrics-api</artifactId>
    <version>2.0.0</version>
</dependency>

There are no functional changes since tag 2.0
For changes consult the changelog.html file, which also clearly indicates the breaking changes.
The changelog is also part of the spec documents.

Assets 5

@pilhuhn pilhuhn released this May 14, 2019 · 20 commits to master since this release

To use this version in your code, include the following in your Maven pom:

<dependency>
    <groupId>org.eclipse.microprofile.metrics</groupId>
    <artifactId>microprofile-metrics-api</artifactId>
    <version>2.0</version>
</dependency>

For changes consult the changelog.html file, which also clearly indicates the breaking changes.
The changelog is also part of the spec documents.

Assets 5

@pilhuhn pilhuhn released this May 7, 2019 · 26 commits to master since this release

<dependency>
    <groupId>org.eclipse.microprofile.metrics</groupId>
    <artifactId>microprofile-metrics-api</artifactId>
    <version>2.0-RC1</version>
</dependency>

Changes in 2.0 (see spec document for a nicer rendering of the list):

  • Refactoring of Counters, as the old @counted was misleading in practice.

    • Counters via @counted are now always monotonic, the monotonic attribute is gone. The Counted interface lost the dec() methods.
    • Former non-monotonic counters are now @ConcurrentGauge and also in the output reported as gauges.
    • See Migration hints about migration of applications using MicroProfile Metrics.
  • Removed unnecessary @InterceptorBinding annotation from org.eclipse.microprofile.metrics.annotation.Metric.

  • Removed deprecated org.eclipse.microprofile.metrics.MetricRegistry.register(String name, Metric, Metadata)

  • Metadata is now immutable and built via a MetadataBuilder.

  • Introduced a Tag object which represents a singular tag key/value pair.

  • Metrics are now uniquely identified by a MetricID (combination of the metric’s name and tags).

  • MetricFilter modified to filter with MetricID instead of name

  • The 'Metadata' is mapped to a unique metric name in the MetricRegistry and this relationship is immutable.

  • Tag key names for labels are restricted to match the regex [a-zA-Z_][a-zA-Z0-9_]*.

  • Tag values defined through MP_METRICS_TAGS must escape equal signs = and commas , with a backslash .

  • JSON output format for GET requests now appends tags along with the metric in metricName;tag=value;tag=value format. JSON format for OPTIONS requests have been modified such that the 'tags' attribute is a list of nested lists which holds tags from different metrics that are associated with the metadata.

  • OpenMetrics format - formerly called Prometheus format

    • Reserved characters in OpenMetrics format must be escaped.

    • In OpenMetrics output format, the separator between scope and metric name is now a _ instead of a :.

    • Metric names with camelCase are no longer converted to snake_case for OpenMetrics output.

    • The default value of the reusable attribute for metric objects created programmatically (not via annotations) is now true

  • Some base metrics' names have changed to follow the convention of ending the name of accumulating counters with total.

  • Some base metrics' types have changed from Counter to Gauge since Counters must now count monotonically.

  • Some base metrics' names have changed because they now use tags to distinguish metrics for multiple JVM objects. For example, each existing garbage collector now has its own gc.total metric with the name of the garbage collector being in a tag. Names of some base metrics in the OpenMetrics output are also affected by the removal of conversion from camelCase to snake_case.

  • Added a set of recommendations how application servers with multiple deployed applications should behave if they support MP Metrics.

Assets 4
Apr 16, 2019
[maven-release-plugin] copy for tag 2.0-SNAPSHOT-3
Mar 19, 2019
[maven-release-plugin] copy for tag 2.0-SNAPSHOT-2.1
Mar 19, 2019
[maven-release-plugin] copy for tag 2.0-SNAPSHOT-2
You can’t perform that action at this time.