Accidental strict dep on LatencyUtils
See original GitHub issueIt seems there are some guards to try to not use LatencyUtils unless pause detection is in use. However, there’s still a compile dep.
[INFO] Caused by: java.lang.ClassNotFoundException: org.LatencyUtils.IntervalEstimator
[INFO] at java.net.URLClassLoader.findClass(URLClassLoader.java:471) ~[?:?]
[INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:588) ~[?:?]
[INFO] at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:93) ~[zipkin-server-2.16.3-SNAPSHOT-slim.jar:?]
[INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
[INFO] at io.micrometer.prometheus.PrometheusMeterRegistry.newTimer(PrometheusMeterRegistry.java:176) ~[micrometer-registry-prometheus-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.MeterRegistry.lambda$timer$2(MeterRegistry.java:271) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.MeterRegistry.getOrCreateMeter(MeterRegistry.java:576) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.MeterRegistry.registerMeterIfNecessary(MeterRegistry.java:529) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.MeterRegistry.timer(MeterRegistry.java:269) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.Timer$Builder.register(Timer.java:477) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.MeterRegistry.timer(MeterRegistry.java:396) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.internal.TimedExecutorService.<init>(TimedExecutorService.java:40) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.binder.jvm.ExecutorServiceMetrics.monitor(ExecutorServiceMetrics.java:94) ~[micrometer-core-1.2.1.jar!/:1.2.1]
[INFO] at io.micrometer.core.instrument.binder.jvm.ExecutorServiceMetrics.monitor(ExecutorServiceMetrics.java:107) ~[micrometer-core-1.2.1.jar!/:1.2.1]
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
micrometer-metrics/micrometer v1.10.0-M3 on GitHub
Fix generic parameters for composite observations #3173 · Service descriptor files not merged/transformed in statsd shadowJar #3268 · Accidental strict dep on ......
Read more >LatencyUtils by giltene
LatencyUtils : A latency stats tracking package. The LatencyUtils package includes useful utilities for tracking latencies. Especially in common in-process ...
Read more >Cloud Native Core Licensing Information User Manual
IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, ...
Read more >Open Source Used In Crosswork Change Automation ... - Cisco
incidental, or consequential damages of any character arising as a ... ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR.
Read more >TrueVueOSS - Sensormatic
LatencyUtils 2.0.3. Creative Commons Public Domain Dedication License. Lettuce5.0.4.RELEASE. Apache License 2.0. Log4J API2.10.0. Apache License 2.0.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like HdrHistogram is also effectively mandatory, It would be nice for these to be optional.
If you are not configuring a pause detector, you can exclude the LatencyUtils dependency. If you are not configuring client-side percentiles, you can exclude the HdrHistogram dependency.