Transactions in Browser

In cases where the Plumbr Browser Agent is present in the end user’s browser, transaction monitoring starts in the browser. The Plumbr Browser Agent keeps track of the interactions performed by the end user. The tracked interactions include mouse and keyboard events, scrolling, tapping on touch screens and many other events through which modern web applications expose their functionality.

Only some of the user interactions start a transaction. A transaction is started whenever the user interaction results in at least one HTTP request being sent to the backend. So for example, a click on an HTML anchor scrolling the page to the location of the anchor will not start a transaction, as no server-side requests are made.

All HTTP requests (called spans in Plumbr lingo) triggered by the interaction are also monitored and linked with the transaction the spans belong to. All spans register the start and end timestamp of the request, the URL to which the request was sent and the HTTP response code of the request.

Browser transaction ends when the last span in the browser is completed. Based on the duration of the transaction and the response codes of the individual spans, the transaction is flagged either as successful, too slow, or having failed to deliver the expected outcome.

User interaction monitored by APM

Transactions also keep track of the user performing the interaction, the application in which the interaction was performed, and the functionality that the interaction consumed. This allows you to keep track of what the particular user was actually doing within the application.

Every transaction starting in a browser thus monitors and exposes the following information:

  • the ID of the transaction
  • the ID of the user performing the interaction
  • the start and end timestamps of the interaction
  • the application to which the interaction belonged
  • the functionality of the application used
  • the outcome of the interaction (successful/slow/failed)