The standalone UI is made available with no additional configuration. If you’re working with headless web services, simply navigate to the application context root and add /xrebel at the end of the URL. For example: http://localhost:port/yourapp/xrebel.
And boom! There you have it – all the goodness of XRebel in its own dedicated browser tab.
If you need to investigate the stack traces of some request, the data is still at your fingertips as you can start and stop data collection at any time. Minimal request details are captured if Profiling is disabled.
Requests with Profiling stopped are labeled with and requests with Profiling started are labeled with so you can easily identify the requests as they aggregate.
Even if your front end is hosted on a non-Java server, you can view backend activities in the XRebel toolbar as you make AJAX requests to a Java backend. The XRebel toolbar can be injected into your HTML with just a snippet of code.
This makes finding the relevant info much easier, even when using trace level logging. This scales particularly well with AJAX-heavy single page apps, because logs for every request are displayed separately. We didn’t stop there – when you log an object we’ll display it like a debugger would, as an expandable object tree!
SLF4J is currently supported with more logging framework support upcoming.
We filter out irrelevant traces showing you immediately the root cause so you can do less digging. Of course, you can view the full stack traces if you want to. Exceptions caused by IO are linked to the Calls view so you can easily find more details.
The XRebel agent will be enabled for the configured WTP servers in your workspace. As XRebel doesn’t require any additional configuration, it’s just a one-step process to get started. Install the plugin, start the server. Voila!
The XRebel agent collects performance data from every application involved in the transaction so you’ll be able to view end to end data in a single view.