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

**URL:** <https://discuss.elastic.co/t/no-transaction-traces-with-elastic-apm-agent-with-quarkus/350232>\
**Category:** APM\
**Tags:** java\
**Created:** [January 2, 2024, 11:58am UTC](https://discuss.elastic.co/t/no-transaction-traces-with-elastic-apm-agent-with-quarkus/350232 "2024-01-02T11:58:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hzdb5betrieb](https://avatars.discourse-cdn.com/v4/letter/h/f475e1/32.png) [@hzdb5betrieb](https://discuss.elastic.co/u/hzdb5betrieb)\
**Post date:** [January 2, 2024, 11:58am UTC](https://discuss.elastic.co/t/no-transaction-traces-with-elastic-apm-agent-with-quarkus/350232/1 "2024-01-02T11:58:46Z")

</div>

**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)

```auto
-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)**:

```auto
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

```

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [January 4, 2024, 3:47pm UTC](https://discuss.elastic.co/t/no-transaction-traces-with-elastic-apm-agent-with-quarkus/350232/2 "2024-01-04T15:47:42Z")

</div>

Hi, the Elastic Java APM agent doesn't currently have instrumentation for Quarkus, the [tech we support is listed here](https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html).

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](https://www.elastic.co/guide/en/apm/guide/current/open-telemetry.html) configuration

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 1, 2024, 3:47pm UTC](https://discuss.elastic.co/t/no-transaction-traces-with-elastic-apm-agent-with-quarkus/350232/3 "2024-02-01T15:47:58Z")

</div>

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