@Yogeshwar.Kabra ,
Are you troubleshooting a performance issue or are you planning on actively and continuously monitoring the performance of your APIs?
I ask because, in addition to the options discussed here, you also have a couple of other options.
If you’re trying to find the root cause of a particular performance issue, then you may want to consider using a webMethods profiler. If, however, you’re hoping to monitor the performance of your APIs continuously, then using an observability agent on your Integration Server to send the data to an APM platform may be of interest. Depending on the agent, you may even get insights similar to what you would get from a profiler.
Full disclosure: I work for a company that offers both and I’d be happy to chat more if you have any questions.
For example, here’s a screenshot from Grafana + Tempo showing a list of API’s and top-level services executed on webMethods sorted by Duration:
You can then drill into one of those traces to see everything that contributed to the total execution time:
Hope this helps,
Percio
#webMethods-io-Integration#webMethods-io-B2B#Integration-Server-and-ESB#Service-Designer#B2B-Integration#webMethods#webMethods-cloud