Elastic APM configuration for Webmethods

Hi all,

This is my first post. I am trying to get webmethods IS server monitoring via Elastic APM agent. I get all the internal services of Webmethods into APM but not able to see the custom jobs I create. I would like to check if someone has done this before and share some best practices in this regards.

Config used

wrapper.java.additional.401=-javaagent:D:\Webmethods\IntegrationServer\lib\jars\custom\elastic-apm-agent-1.52.0.jar
wrapper.java.additional.402=-Delastic.apm.service_name=IS_DEFAULT
wrapper.java.additional.403=-Delastic.apm.server_url=<APM url>
wrapper.java.additional.404=-Delastic.apm.secret_token=<......>
wrapper.java.additional.405=-Delastic.apm.application_packages=com.wm.app.b2b.server,com.wm.lang.flow,Messaging.durableSubscriber
wrapper.java.additional.406=-Delastic.apm.hostname=<hostname>
wrapper.java.additional.407=-Delastic.apm.verify_server_cert=false
wrapper.java.additional.408=-Delastic.apm.trace_methods=com.wm.app.b2b.server.*,test.*,Messaging.durableSubscriber.*

Kibana version: 8.15

Elasticsearch version: 8.15

APM Server version: 8.15

APM Agent language and version: 1.52 - Java agent

Browser version: Edge, Chrome

Original install method (e.g. download page, yum, deb, from source, etc.) and version: download page

Fresh install or upgraded from other version? Fresh cloud deployment

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.

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

Steps to reproduce:
1.
2.
3.

Errors in browser console (if relevant):

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

If the custom jobs are created programmatically, you can use an annotation like @CaptureTransaction to trace those. If not, you'll need to find the job initiating class and add it to your trace_methods

Thanks for the suggestion. The services are already built and are in Production. I was doing some checks on other available solutions for webmethods - AppDynamics and OTelscope. Both solutions have some packages that need to be deployed onto the Integration server of Webmethods post which the metrics are collected at each service instance level. I have not found much information around Webmethods using Elastic APM.

Then the only option I can suggest is to extend your usage of trace_methods to add in the same methods that you would annotate - it's the same effect, starting a transaction from that method

1 Like