If you’ve ever wondered what your services are calling, you’ll love our new Service flow feature.
Ruxit understands your applications’ transactions from end-to-end. We use these transactional insights to construct smartscape topological views of all your services, including your infrastructure. As smartscape is a topological model however, it necessarily lacks detail about individual requests and response-time contributions.
Service flow isn’t a topological overview. Service flow shows the actual execution of each individual service and service-request type. Whereas smartscape shows you your overall environment topology, Service flow provides you the view point of a single service or service-request type.
The screenshot below shows what the
orange-booking-payment.jsf web request of the
EasyTravelWebServer service triggers in your system and how each component contributes to the overall response time. As you can see, this perspective provides far more detail than smartscape view.
EasyTravelWebServer service calls a Tomcat, which in turn calls two other services, which in turn call two more services. What becomes immediately apparent is that the
Credit Card Verification service contributes the most to overall response time, although its caller,
BookingService, is only called by 28% of the requests. This degree of analysis enables you to understand the bigger complexities within your system.
As you can see, service flows can become highly complex:
Ruxit does two things to help you navigate extensive service-flow data:
- The amount of data displayed in Service flow view dynamically resizes based on the size of your browser window. So you can maximize/minimize your browser window to increase/reduce the amount of service-flow data you analyze. You can also use your browser’s zoom function to display more/less data.
- Service flow focuses on what’s most important to customers: response-time contribution.
Service flow aggregates services that contribute little to overall response time.
That said, you can still analyze the service flow structure of aggregated response-time contributors. In the screenshot below you can see that Ruxit is focused on the
RMI Server service. Ruxit highlights the call flow to this service in blue and shows you that, while the
easyTravel Customer Frontend service calls the
RMI Server 4.5% of the time, if you consider the entire sequence beginning with the
EasyTravelWebserver service, you can see that the
RMI Server service is called by only 4% of requests. This is because
easyTravel Customer Frontenditself is called less than 100% of the time, which lowers the overall contribution.
As you surely have a keen eye, you likely noticed that some of the services in the above Service flow screenshot appear multiple times (
easyTravel Customer Frontend and
EasyTravelWebserver). This is because these services were called at multiple points during the flow of this transaction. Each call performs different actions and contributes different amounts to the overall response time. Ruxit doesn’t aggregate these varying circumstances into a single metric because individually they are significant and provide a valuable picture of what’s going on at a very deep level in your environment.
How do I access Service flow?
Service flow is available for both complete services and individual requests. Just select Service flow from the More (…) menu on any service or service-request page.