search

elastic / apm-agent-rum-js

https://www.elastic.co/guide/en/apm/agent/rum-js/current/index.html
MIT License
275 stars 133 forks source link

Provide configuration to group http-request transactions #577

Open hmdhk opened 4 years ago

hmdhk commented 4 years ago

http-request transactions currently capture the method and url as the transaction name, however the url could include unique ids which would result in many transaction groups in the APM UI. We can also potentially provide a grouping mechanism for all transactions on the agent side, e.g. using regex.

More detail: https://discuss.elastic.co/t/elastic-apm-rum-js-agent-grouping-http-request-transactions/215380

vigneshshanmugam commented 4 years ago

This should be already possible by the users with two solutions

  1. Using transaction events transaction:start and transaction:end and changing the name of the transaction to group them accordingly in the UI https://www.elastic.co/guide/en/apm/agent/rum-js/current/agent-api.html#observe
  2. using filers https://www.elastic.co/guide/en/apm/agent/rum-js/current/agent-api.html#apm-add-filter and changing the transaction name.

We can add these to docs till the UI is able to handle nested transaction levels.

vigneshshanmugam commented 4 years ago

Can we apply the categorisation done for the page load to all managed transactions as well? WDYT?