Tracing elastic search with java agent does not create any transaction

Elastic Observability APM
,
1

Elasticsearch version:
7.6
APM Server version:
8.0.0
APM Agent language and version:
Java/1.18.0

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

We installed elastic search and tried to attach java agent as below

/bin/java -javaagent:/opt/sfagent/sftrace/java/elastic-apm-agent-1.18.0.jar -Delastic.apm.server_urls=https://<url>:443/sftrace -Delastic.apm.verify_server_cert=false -Delastic.apm.global_labels=_tag_appName=elasticsearch,_tag_projectName=sftrace -Delastic.apm.log_level=TRACE -Delastic.apm.log_file=/opt/sfagent/sftrace/trace.log -Xms256m -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.foreground=yes -Des.path.home=/usr/share/elasticsearch -cp :/usr/share/elasticsearch/lib/elasticsearch-1.7.3.jar:/usr/share/elasticsearch/lib/*:/usr/share/elasticsearch/lib/sigar/* -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.conf=/etc/elasticsearch org.elasticsearch.bootstrap.Elasticsearch

Though metrics data is sent, we cannot see any transactions or spans getting captured.

We triggered the below es request after attaching the agent and starting es
http://:9200/_nodes/settings?pretty=true

As per logs, agent is getting attached, but transactions/http requests are captured.

Could you pls suggest if there is any config change we need to do.

We are mainly doing this because we are facing an issue with attaching an agent in one of the spring boot applications. So want to check if we are seeing the same issue in tracing elastic search as well.

Thanks,
Priya

2

Hi @priya.narasimhan,

Unfortunately, Elasticsearch is not yet supported by our APM agent. This is due to the lack of a proper plugin to support the HTTP layer used by Elasticsearch.

However, what you could do is to instrument the application that calls Elasticsearch with an APM agent, thus that would provide more insights on what is being executed on ES.

3

OK, Thanks for the information.

4

Also, if you need any help with ES performance and profiling, here are a couple of links that could be relevant.

5

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