Bootstrap FreeKB - OpenShift - Resolve "Error trying to connect to APM Server"
OpenShift - Resolve "Error trying to connect to APM Server"

Updated:   |  OpenShift articles

Let's say you have a Tomcat application server that is being monitored by Elastic APM (Application Performance Monitoring), and the following is found in the Elastic APM log on the Tomcat application server.

2021-10-04 22:17:10,022 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error trying to connect to APM Server. Some details about SSL configurations corresponding the current connection are logged at INFO level.

 

Notice "Error trying to connect to APM Server". The elasticapm.properties file will contain the URL of the APM Server.

~]$ grep url /usr/local/elastic/elasticapm.properties
server_urls=https://apm.example.com:443

 

Check to see if the URL responds to a ping.

~]$ ping -c4 apm.example.com
64 bytes from 10.64.147.134: icmp_seq=1 ttl=254 time=0.476 ms
64 bytes from 10.64.147.134: icmp_seq=2 ttl=254 time=0.242 ms
64 bytes from 10.64.147.134: icmp_seq=3 ttl=254 time=0.323 ms
64 bytes from 10.64.147.134: icmp_seq=4 ttl=254 time=0.229 ms

4 packets transmitted, 4 received, 0% packet loss, time 3002ms

 

If you are able to ping the Elastic APM sytem, then it may make sense to update the elasticapm.properties file to log events at log level DEBUG, and to restart the implacted application servers so that they log events at log level DEBUG.

log_level=DEBUG

 




Did you find this article helpful?

If so, consider buying me a coffee over at Buy Me A Coffee



Comments


Add a Comment


Please enter b72c14 in the box below so that we can be sure you are a human.