Advanced features

This chapter details advanced configuration options for QRebel. Please head over to for more information about QRebel.

Microservices configuration

In order to profile distributed applications or microservices, add QRebel Agents to all connected applications.


Keep in mind that there are two methods to collect microservices transactions:

  1. Configuring all applications to share the same name. All traces will be collected into one application view on the dashboard using that name.
  2. Using separate names for all connected applications. Transactions are separately collected and displayed under each separate application. The top level applications will still display all transactions from connected applications.


End-to-end transactions will be highlighted using the remote2icon icon.

Custom profiling

QRebel Agents can be configured to use a customized profiling setup. This is useful for adding requests that would normally not be picked up by QRebel (e.g. desktop applications, non-HTTP requests). To do this:

  1. Download the customized configuration file.
  2. Edit the file to set up customized entry points. Detailed instructions are contained within.
  3. Save the file in the same location as the QRebel Agent JAR file.
  4. Restart your application.

Multiple applications running in a single container

Multiple applications running in a single container can be detected using the following VM argument: -Dqrebel.app_auto_discovery=true (defaults to false).

The application name is read form the <display-name> element of your web.xml. When not provided, the application’s context root is displayed as the application name in QRebel.