There are metrics that are automatically captured by the agent, in seems in your case that some of them are sent with an incompatible format to the APM server ?
Can you provide the full version of the Elastic APM Java agent used here ? There are quite a few in the 1.x range. The simplest would be to update to the latest 1.23.0 as of today just to be sure it's not something that has been already fixed in the agent.
If updating the agent does not make the problem go away, then the next step is to set log_level=debug and to see which metrics are being sent for more details.
Hi all! We have been facing the same issue with different Java Agent versions. For us it is connected to Kafka, but reading this thread I'm assuming that it is a more general problem?
APM Java agent v1.20.0, v1.22.0 and v1.23.0 with APM Server version 7.11.1
The error messages on our side are connected to Kafka samples which (sometimes) seem to be missing. The error messages didn't change after updating the agent version.
co.elastic.apm.agent.report.IntakeV2ReportingEventHandler: Error sending data to APM server: Server returned HTTP response code: 400 for URL: https://apm.our-domain.example.com:9243/intake/v2/events, response code is 400
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.