ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - open-telemetry

I am trying to connect my application to Signoz. It only works when both application and Signoz are running in the same machine. If I pull the application in another machine, I am getting timed out error.
ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export spans. The request could not be executed. Full error message: connect timed out
My application is deployed in Wildfly so I have add the following JAVA_OPTS to the standalone.conf.bat
set "JAVA_OPTS=%JAVA_OPTS% -javaagent:c:/signoz/opentelemetry-javaagent.jar -Dotel.metrics.exporter=none -Dotel.exporter.otlp.endpoint=http://MyOtherServer:4318 -Dotel.resource.attributes=""service.name=MyService"""

opentelemetry-javaagent by default expects gRPC protocol that is usualy listening on port 4317.
If your collector listens on 4318, it is otlp-http. That means you must also set
-Dotel.exporter.otlp.protocol=http/protobuf
Source: https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#otlp-exporter-span-metric-and-log-exporters

Related

RabbitMQ Stream Exception using a Dockerized Spring Boot Application

When starting up Spring Boot I get the following error:
Failed to start bean
'org.springframework.amqp.rabbit.config.internalRabbitListenerEndpointRegistry';
nested exception is com.rabbitmq.stream.StreamException
and the cause of the error is:
java.net.UnknownHostException: 4e31343111e9: Temporary failure in name
resolution
The authentication passes fine for RabbitMQ - if I change the credentials then it fails at that before even reaching this stage.
Spring Boot is running using a Docker container and the RabbitMQ host is also on another host running in a container (with 5552 port open).
The error was that there was no advertised host and port for streams in the rabbit instance - this was resolved once that was added as the explicit host IP address.

Debugger failed to attach: handshake failed - received >GET /api/domai< - expected >JDWP-Handshake<

I am trying to debug a basic Quarkus app by running the command ./mvnw compile quarkus:dev on IntelliJ (as stated in the Quarkus docs) and it seems to run ok (gives me the following message: Listening for transport dt_socket at address: 5005)
I can call the APIs on port 8080 and all fine but when I try to call the same API on port 5005 I get the following error Debugger failed to attach: handshake failed - received >GET /api/domai< - expected >JDWP-Handshake<.
I tried configuring a Remote Debug configuration as shown in the image but doesn't seem to work.
Does anyone know how to solve this?
One process can listen on multiple TCP/IP sockets for multiple things.
The debug port is the port 5005 where you attach the remote debugger to.
The API calls still need to go to port 8080, though. When you hit a breakpoint, you will see it in your debugger.

What is the right host url in sonar for bamboo(plugin) configuration?

I have to set host url in sonar for bamboo(bambo plugin) configuration.
While my local docker program is running sonarqube container, it is confused to use localhost:9000 at host url in app configuration.
The error message is saying An error occurred while connecting the given SonarQube server: localhost:9000 failed to respond.
What should I do? Am I doing wrong or Is there anything to set more thing?
enter image description here
As your SonarQube instance is running in a different server, you need to point your "Sonar for Bamboo" plugin to that server, port 9000 (default of SonarQube). So, for example, if your server containing the SonarQube instance has the IP address 192.168.15.1 in your network, you need to configure the plugin to http://192.168.15.1:9000.
I did it in my environment and it works perfectly.

Getting " Logs eventsource failed with: 400 Bad Request" in Heroku logs

I am trying to understand why my JHipster app is not working when i deploy it to Heroku (It does locally) so my first thought was going to the logs. However when i type $ heroku logs i receive back the following error.
571 borgesan:~/bitbucket/eureka $ heroku logs -n 200
▸ Logs eventsource failed with: 400 Bad Request
What could be causing this error?
I encounter exactly the same log message when deploying a kotlin app that works locally with 'heroku local web'. The web app is based on a jetty server running on port 5000 (same port as in the kotlin-getting-started example, but different web server).
In parallel, all requests to server are refused with 503 Service available
Is there a parameter to set somewhere in the heroku configuration or procfile to declare internal port 5000 (to allow mapping between outside port 80 or 443 to internal port 5000)?
Is it a problem due to CORS or so ? In other words, shall the application accept specific fields of request header ?
other thing to take care of ?
Thanks

Getting NettyTcpClient connection error with Spring WebSocket with amqp broker (rabbitmq) while running in docker

I am trying to use the rabbitmq as the StompBroker in the WebSocketConfig. Have added the dependencies reactor-core and reactor-net
It works fine when starting up locally (localhost) but when I try to start the project as a docker container (rabbitmq image is correctly built with STOMP plugin), I get below error.
r.io.net.impl.netty.tcp.NettyTcpClient : Failed to connect to /127.0.0.1:61613. Attempting reconnect in 5000ms
I tried setting the setRelayHost("rabbitmq") and setRelayPort(61613) (since rabbitmq is the service name in the docker compose, using it to resolve the host name). No luck still.

Resources