Closed cut-to-the-cheese closed 5 years ago
This does seem to work: https://github.com/jahanzebbaber/vertx-micrometer-metrics/commit/938a4038f7d1d6df283621f2cb31a6d60669d894 Happy to raise a PR if this is indeed an acceptable fix.
Hi @jahanzebbaber , thanks for reporting
Happy to raise a PR if this is indeed an acceptable fix.
Yes please, a PR is welcome
Raised a PR with a brand new branch: https://github.com/vert-x3/vertx-micrometer-metrics/pull/76
I'm closing, PR was merged. Thank you @jahanzebbaber
Setting up vertx metrics options like this causes NPE whenever you try to hit the http server:
The issue is pretty easily reproducible. In PrometheusMetricsITest's shouldStartEmbeddedServer test, I have added the same LabelMatch and the test does fail: https://github.com/vert-x3/vertx-micrometer-metrics/commit/9b35c7775d71ffc427de1b10cdff33a7a2fa3c69?diff=split
The stack trace I have from my application is bit different however. It originates from VertxNetServerMetrics from where some of the internal metrics are being reported:
I have tried excluding metric categories as well but no luck:
.setDisabledMetricsCategories(EnumSet.of(MetricsDomain.DATAGRAM_SOCKET, MetricsDomain.NAMED_POOLS, MetricsDomain.NET_CLIENT, MetricsDomain.NET_SERVER))