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

Improved XRebel UI for tracking HTTP invocations, SQL and NoSQL queries

The first post in this series we focused on how organizing I/O data made the XRebel UI simple and scalable for Java enterprise apps.

In this post, let’s take a look into how XRebel presents SQL queries, HTTP invocations and NoSQL queries…

Consistency anyone?

XRebel tracks multiple event types– SQL queries, HTTP invocations and NoSQL queries. Given that these are different event types, different sets of attributes have to be presented to you without changing contexts or tools. Presenting the data in a consistent manner that is coherent with the design, is obviously critical.

Let’s address SQL queries first. SQL queries can sometimes be too long and inconvenient to read. We decided to add some eye candy by formatting the tracked SQL query and adding basic syntax highlighting. As an added bonus, you can easily copy and paste the pre-formatted text into other tools for further editing or testing.

xrebel-sql-formatting

Next up: HTTP calls. The outgoing HTTP calls include a lot of useful details: the URL, request headers, response headers, response body, and status code. In keeping with the theme of presenting data consistently, the details of a HTTP request are rendered as expandable blocks. This makes it convenient to browse the grouped data.

xrebel-http-calls

Lastly let us see how XRebel handles NoSQL queries. In the case of MongoDB queries, it is handy to show how many network roundtrips are triggered while iterating over the result’s cursor. This is a nice little detail that helps you make decisions when optimizing the batch size of the query.

The not-so-obvious fact about MongoDB support in XRebel is that the queries are rendered in a Mongo shell compatible syntax . With the way that XRebel presents this data to you, if you want to run the query yourself, you can just copy and paste it into the console. This eliminates the need to manually tune the syntax before execution.

xrebel-mongodb-roundtrips

We believe that focusing on these minute design details makes XRebel a delight to use! Let us know if you agree by leaving a comment here or on on Twitter – @zeroturnaround . Watch this space for our final post in this series on how users get a choice of viewing information that is most relevant to them. Come back for more!

Ready to explore the awesomeness of XRebel? TRY XRebel for Free Now!