# APM agent not showing transaction logs on Jboss Fuse Pods deployed in Openshift **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [June 4, 2020, 11:23am UTC](https://discuss.elastic.co/t/apm-agent-not-showing-transaction-logs-on-jboss-fuse-pods-deployed-in-openshift/235744 "2020-06-04T11:23:08Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![khgupta3](https://avatars.discourse-cdn.com/v4/letter/k/b3f665/32.png) [@khgupta3](https://discuss.elastic.co/u/khgupta3)\ **Post date:** [June 4, 2020, 11:23am UTC](https://discuss.elastic.co/t/apm-agent-not-showing-transaction-logs-on-jboss-fuse-pods-deployed-in-openshift/235744/1 "2020-06-04T11:23:08Z")
I have installed APM Java agent "elastic-apm-agent-1.15.0.jar " on the VM where my pod is running. The APM Server configuration is running fine with Jboss EAP application but when we are using Jboss Fuse application only JVM data is getting fetched and not the transactional data. APM Server is reachable from this machine. Please assist where I am doing wrong. We are using Basic version. Elasticsearch Version: 7.6.0 Kibana Version : 7.6.0 APM Server Version: 1.15.0 JAVA version: openjdk version"1.8.0\_191" Changes in the Server yml used to restart the pod is as below -Delastic.apm.server\_urls=http://10.131.111.32:8200 -Delastic.apm.service\_name=ESB -Delastic.apm.hostname=ESB\_Account -Delastic.apm.log\_level=DEBUG -Delastic.apm.log\_file=/home/devops/apm/log/elastic-apm.log -Delastic.apm.enable\_log\_correlation=true -javaagent:/home/devops/apm/elastic-apm-agent-1.15.0.jar ---
**Author:** ![Eyal\_Koren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_koren/32/36830_2.png) [@Eyal\_Koren](https://discuss.elastic.co/u/Eyal_Koren)\ **Post date:** [June 4, 2020, 2:22pm UTC](https://discuss.elastic.co/t/apm-agent-not-showing-transaction-logs-on-jboss-fuse-pods-deployed-in-openshift/235744/2 "2020-06-04T14:22:34Z")
Hi and welcome to the forum! First, try setting the suggested value for Fuse for the [`boot_delegation_packages`](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-boot-delegation-packages) config option. You would get auto-instrumentation tracing depending on which technologies you are using. See [this comment](https://discuss.elastic.co/t/monitoring-jboss-fuse-using-apm/185758/12) and the rest of the contents of this topic. If you don't get what you want out of the box, you may use manual instrumentation instead. ---
**Author:** ![khgupta3](https://avatars.discourse-cdn.com/v4/letter/k/b3f665/32.png) [@khgupta3](https://discuss.elastic.co/u/khgupta3)\ **Post date:** [June 5, 2020, 11:06am UTC](https://discuss.elastic.co/t/apm-agent-not-showing-transaction-logs-on-jboss-fuse-pods-deployed-in-openshift/235744/3 "2020-06-05T11:06:33Z")
> [@khgupta3](#): > > openjdk version"1.8.0\_191" Thank Eyal for your time. I added boot\_delegation -Delastic.apm.server\_urls=[http://10.131.111.32:8200](http://10.131.111.32:8200) -Delastic.apm.service\_name=ESB -Delastic.apm.hostname=ESB\_Adjustment -Delastic.apm.boot\_delegation\_packages=org.apache.karaf.jaas.boot,org.apache.karaf.jaas.boot.principal,org.apache.karaf.management.boot,sun._,com.sun._,javax.transaction,javax.transaction._,javax.xml.crypto,javax.xml.crypto._,org.apache.xerces.jaxp.datatype,org.apache.xerces.stax,org.apache.xerces.parsers,org.apache.xerces.jaxp,org.apache.xerces.jaxp.validation,org.apache.xerces.dom,co.elastic.apm.agent.\* -javaagent:/home/devops/apm/elastic-apm-agent-1.15.0.jar" But after adding and doing "oc apply -f xyz.yaml", I even couldn't see that pod in JVM. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2020, 11:06am UTC](https://discuss.elastic.co/t/apm-agent-not-showing-transaction-logs-on-jboss-fuse-pods-deployed-in-openshift/235744/4 "2020-07-05T11:06:37Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.