Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19503

New OpenTelemetry image version v0.104.0 doesn't work with QS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 33.0.0.Final
    • None
    • Quickstarts
    • None
    • Hide
      • Download QS
      • Configure and start the EAP server
      • Check the error
        • Check the logs in case of Micrometer QS
        • Start the integration test and check reported statistic in case of OpenTelemetry QS 
      Show
      Download QS Configure and start the EAP server Check the error Check the logs in case of Micrometer QS Start the integration test and check reported statistic in case of OpenTelemetry QS 
    • ---
    • ---

      A new docker image of OpenTelemetry collector (v0.104.0) is not compatible with our Mircometer and OpenTelemetry QS. 

      After micrometer extension configuration the server will start produce the following warning message

      14:52:28 12:52:28,574 WARNING [io.micrometer.registry.otlp.OtlpMeterRegistry] (otlp-metrics-publisher) Failed to publish metrics to OTLP receiver: java.net.SocketException: Connection reset
      14:52:28 	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:328)
      14:52:28 	at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:355)
      14:52:28 	at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:808)
      14:52:28 	at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
      14:52:28 	at java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:244)
      14:52:28 	at java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
      14:52:28 	at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:343)
      14:52:28 	at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:826)
      14:52:28 	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:761)
      14:52:28 	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:785)
      14:52:28 	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1688)
      14:52:28 	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589)
      14:52:28 	at java.base/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:529)
      14:52:28 	at io.micrometer@1.9.4.redhat-00002//io.micrometer.core.ipc.http.HttpUrlConnectionSender.send(HttpUrlConnectionSender.java:104)
      14:52:28 	at io.micrometer@1.9.4.redhat-00002//io.micrometer.core.ipc.http.HttpSender$Request$Builder.send(HttpSender.java:305)
      14:52:28 	at io.micrometer@1.9.4.redhat-00002//io.micrometer.registry.otlp.OtlpMeterRegistry.publish(OtlpMeterRegistry.java:109)
      14:52:28 	at io.micrometer@1.9.4.redhat-00002//io.micrometer.core.instrument.push.PushMeterRegistry.publishSafely(PushMeterRegistry.java:54)
      14:52:28 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
      14:52:28 	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
      14:52:28 	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
      14:52:28 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
      14:52:28 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
      14:52:28 	at java.base/java.lang.Thread.run(Thread.java:840)
      

      In case of OpenTelemetry no warning log message is produced but also no statistic are pushed into collector. So the purpose of the OpenTelemetry QS is not fulfilled.

              emartins@redhat.com Eduardo Martins
              emartins@redhat.com Eduardo Martins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: