Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

XRebel UI Hack: View data that is relevant for your app’s performance analysis

Data that you don’t care about? We’ve got a fix for that!

The theme of this series of blog posts post has been showcasing how XRebel is giving users useful information, while keeping it simple. Here are the first two posts, in case you missed it:

One of the features of XRebel is to display server-side activity data of a web application. This resets the state on every page reload so that only the recent data is shown. However, in the case of AJAX-heavy applications, pages do not reload and all the data is preserved. This is especially true in case of single page applications, where a page would only be rendered once.

XRebel handles AJAX requests by appending the request data to the bottom of the current view. In case the subsequent calls are executed against the same resource, the entries are grouped together.


A very common behavior of AJAX applications is periodically polling for data from the server. Such requests often do not provide anything of interest and the view is polluted with the unnecessary data. Oh no, so this particular data is NOT useful. So let’s fix it right?

XRebel gives the user the ability to filter out the unwanted requests. All you have to do is hover over the desired request line, you will see a minus button, click on it, and boom, the requests are hidden. This can be used to hide the request with all its data.


This solution turned out to be quite handy for quickly hiding the unwanted requests. Changed your mind about hiding them and want to know how to restore the hidden request? XRebel has that covered as well. Right above the data view you can find the Hidden items checkbox. By selecting this option, you will see all hidden requests. You can “unhide” the requests by hovering on the entry line and clicking the plus button that will appear. Simple!


This simple solution for hiding and restoring the data entries worked out surprisingly well. The same logic can be applied to the individual IO entries. This allows for opting out of the audit queries that you are not interested in. How awesome is that?!

In conclusion

Designing a simple UI for complex data is challenging, yet surprisingly motivating! We progressed through different design steps by experimenting with different options for presenting the data that the XRebel agent logs during application execution. The end result is rather amazing – the feedback that we have received from our clients is very positive! We take this as a big compliment. Thank you!

Impressed? Leave your comments below or mention us on twitter – @zeroturnaround . You can also send us an email –

TRY XRebel for Free Now!