Stop collecting data from host using java apm agent(1.7.0)

Elasticsearch version: 7.2.0

APM Server version: 7.2.0

APM Agent language and version: elasticapm-java 1.7.0

Original install method (e.g. download page, yum, deb, from source, etc.) and version: docker

Provide logs and/or server output (if relevant):

{"log":"2019-08-01T09:50:29.455Z\u0009ERROR\u0009[request]\u0009beater/intake_handler.go:94\u0009error handling request\u0009{"request_id": "f9a2907a-1904-41c3-85a1-68aebf2f91ec", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "", "user-agent": "elasticapm-java/1.7.0", "error": "read tcp :8200-\u003e10.10.32.106:55836: i/o timeout"}\n","stream":"stderr","time":"2019-08-01T09:50:29.455880829Z"}

Hi and thanks for trying Elastic APM,

It is a little difficult to help with such limited information however the error

error": "read tcp :8200-\u003e10.10.32.106:55836: i/o timeout"}

Appears to indicate the agent can not connect to the apm-server

Please provide how you start the Java Application with the agent and what agent configuration parameters you use?

When you start the Application with the agent you should see a line in the log near the beginning that looks like

2019-08-01 21:54:17.616 [apm-server-healthcheck] INFO - Elastic APM server is available: { "build_date": "2019-07-24T17:14:06Z", "build_sha": "a6b6ca2f36a7b3fd3dfe74840fed0ef9d67cb046", "version": "7.3.0"}

Do you see that? or does it say something like this which mean the Agent can not connect to the apm-server.

2019-08-01 21:44:41.422 [apm-server-healthcheck] WARN - Elastic APM server is not available (Connection refused (Connection refused))

Another set of questions:
Is there a load balancer between the agent and the APM Server? Is that a sporadic error? Does it happen right after starting the application? Only after a certain amount of time?

Thanks for your prompt response here.

We are not using any load balancer. It was working fine after the set-up , it completely stop collecting the data after sometime with the error message as i mentioned.

We are running the basic default configuration for agent by following the below approach.

Do you have the agent logs available for this timeframe?

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.