With technology-specific counters and comprehensive network insights, Ruxit already provides a ton of value in the process-monitoring domain. Ruxit measures many valuable metrics and alerts you whenever problems are detected within processes. Sometimes though, this just isn’t enough.
Particularly when working with network metrics like retransmissions and traffic it’s important that you know the volume and quality of communication between processes. Only then can you properly diagnose and troubleshoot problems that occur within the connections between vital application-infrastructure components.
Ruxit is now capable of tracking crucial performance counters on the process-connections level, so you can easily identify process pairs that have high traffic and connectivity problems. The volume and network quality metrics for process pairs are visualized in the context of the selected host as well as in the context of connections to other processes on other hosts.
To analyze process connections between hosts:
- Click the Hosts tile on your Ruxit homepage.
- Select the host you want to analyze.
- Click one of the Processes boxes (incoming or outgoing) on either side of the Hosts infographic to view:
- Number of processes involved in each communication
- Transfer rate
- Number of newly established connections per minute
- Click the Analyze process connections button to get more information about process connections and related metrics, as shown below.
Here you can view all connections made and received by the host. Connections are depicted visually in a design that’s similar to smartscape view. The middle column represents the analyzed host. On the left-hand side you see the hosts and processes that connect to the analyzed host; outbound communications are depicted on the right-hand side.
Click any process node (middle column of the infographic) to view relevant network metrics for all that process’ connections (displayed in the right-hand pane). For each connection you’ll see network Transfer, Connectivity, and Retransmissions rates.
If Ruxit detects a network problem, for example TCP retransmissions, you can now precisely pinpoint the affected network links by analyzing on which process connections the problem occurred. In the example below, the outgoing connection from
eT-demo-Frontend-LoadBalancer suffers from a high packet-retransmission rate.