Https backend call is not captured as transaction.type: http-request by RUM javascript agent

Elastic Observability APM
2

Hi @dacothe,

This is indeed the intended behaviour of the RUM agent. There are three distinct transaction types captured by the agent in the order of priority.

  1. If there is a navigation that causes the page load activity, the agent captures them as page-load transaction.
  2. Any subsequent page transitions or SPA navigations that causes change in URL caused by Click/Form Submit gets captured as route-change transaction.
  3. If there are no navigation related events and there are some network requests to the backend that was caused by polling, etc. the agent groups them under http-request.

In your example, it seems like there is a URL change activity that triggered the POST request which then gets associated with the route-change transaction.

You can disable specific transaction types by specifying disableInstrumentations: ["route-change]", but i would not recommend as there might be some missed events as a result of navigations.

Thanks,
Vignesh