Ruxit provides answers, not just data. To this end, we’ve introduced automatic hotspot analysis and an improved service analysis workflow.
On each service page you’ll now see two enhancements:
- The Response time section of each service infographic is now pre-selected by default, so the Response time charts are immediately visible. Of course you can still click other sections of the infographic to see detail regarding other data such as Failure rate and called Services.
- The list of top contributors at the bottom of the page has been removed.
- The most important hotspots in your service are highlighted on the right.
The new hotspots section is dynamic and automatically displays the most important hotspots in your service. Ever wonder which of your requests are the most CPU intensive requests, are the Most time consuming requests, or are the Slowest requests? This information is now gathered and displayed for you automatically.
Click any hotspot entry to begin deeper analysis. In the example above, Ruxit shows you that the most CPU intensive request is the /orange.jsf request. Clicking this entry takes you to a chart that displays overall CPU consumption of this request (shown below). This represents all the CPU cycles that requests of this type consume in your Web server cluster. Click the View method hotspots button to view CPU level hotspots in your code. This is all just two clicks away from each service page!
Of course monitoring isn’t only about resource consumption. Errors are a greater concern. As such, Ruxit immediately informs you of all requests that have high failure rates.
Clicking a request shows you the Failure rate chart for that particular request. Here again you have the option of investigating the root cause of the failures. Just click the View details of failures button.
In this example, Ruxit shows you that the request failures are the result of problems with another service, BookingService.
If you take the next logical step, down to the exception stack trace, you’ll see the root cause of the failures—source code line information included!
When viewing a service page, any Problematic requests related to the service are displayed in the right-hand column.
And when using Ruxit in the context of analyzing a problem, all requests that contribute to the problem are displayed.
Maybe you’re wondering where the list of requests went? It hasn’t moved far—just click the Show all requests button to view them.