No transaction/traces with elastic-apm-agent with quarkus

Kibana version:
7.17.0
Elasticsearch version:
7.17.0
APM Server version:
7.17.0
APM Agent language and version:
java: elastic-apm-agent-1.45.0.jar
Browser version:
firefox latest
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
-javaagent:/elastic-apm-agent/elastic-apm-agent-1.45.0.jar

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
we want to instrument quarkus apps within an container with the -javaagent flag.
(elastic-apm-agent-1.45.0.jar)
apm version 7.17.0

we receive the jvm metrics in apm , but no transaction / spans .
How to make the tranasctions/traces visible in the apm appllication ?

Steps to reproduce:
our configurtion (container-env)

-e ELASTIC_APM_SERVICE_NAME=MYPROJECT \
-e ELASTIC_APM_ENVIRONMENT=myenv \
-e ELASTIC_APM_SERVICE_NODE_NAME=<node_name> \
-e ELASTIC_APM_HOSTNAME=<node_name> \
-e ELASTIC_APM_SERVER_URL=https://<ip>:8200 \
-e ELASTIC_APM_VERIFY_SERVER_CERT=false \
-e ELASTIC_APM_APPLICATION_PACKAGES=* \

Errors in browser console (if relevant):
no errors to see.

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

2024-01-02 12:25:43,560 [main] INFO  co.elastic.apm.agent.util.JmxUtils - Found JVM-specific OperatingSystemMXBean interface: com.sun.management.OperatingSystemMXBean
2024-01-02 12:25:43,597 [main] INFO  co.elastic.apm.agent.util.JmxUtils - Found JVM-specific ThreadMXBean interface: com.sun.management.ThreadMXBean
2024-01-02 12:25:43,615 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.45.0 as <artifact_name> (1.2.1-SNAPSHOT) on Java 17.0.9 Runtime version: 17.0.9+9-LTS VM version: 17.0.9+9-LTS (Red Hat, Inc.) Linux 4.18.0-425.3.1.el8.x86_64
2024-01-02 12:25:43,616 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - service_node_name: '<node_name>' (source: Environment Variables)
2024-01-02 12:25:43,617 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - hostname: '<node_name>' (source: Environment Variables)
2024-01-02 12:25:43,617 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - environment: 'myenv' (source: Environment Variables)
2024-01-02 12:25:43,617 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - sanitize_field_names: 'passwort,password,passwd,pwd,secret,*key,*token*,*session*,*credit*,*card*,authorization,set-cookie' (source: Environment Variables)
2024-01-02 12:25:43,617 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - server_url: 'https://<ip>:8200' (source: Environment Variables)
2024-01-02 12:25:43,617 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - verify_server_cert: 'false' (source: Environment Variables)
2024-01-02 12:25:43,618 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - application_packages: '*' (source: Environment Variables)
2024-01-02 12:25:43,618 [main] INFO  co.elastic.apm.agent.configuration.StartupInfo - log_level: 'TRACE' (source: Environment Variables)
2024-01-02 12:25:45,137 [main] INFO  co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to RUNNING state

Hi, the Elastic Java APM agent doesn't currently have instrumentation for Quarkus, the tech we support is listed here.

If Quarkus instrumentation is essential for you, I would recommend using the OpenTelemetry agent, and pointing at your Elastic APM server, we fully support that configuration

1 Like

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