This post is about the impact of network issues on services and applications. We will introduce all the relevant metrics like the number of retransmissions, etc. Of course, we will also show how to monitor those numbers easily and what that means for your environment.

Application Performance Monitoring is not just about measuring response times of services and applications. For being able to correlate and evaluate all of the collected data in a sophisticated way, processes and their network communication need also be taken into account.

With the latest release, our network monitoring support has reached full production quality and will be available to all customers updating their agents. By enabling this new, exciting functionality, Ruxit will easily be able to answer the following questions:

Which processes consume most of my network resources?

ruxit always provided a meaningful overview of all the metrics that are important for easily gaining a first glance at network utilization. Now we also provide a comprehensive insight on the process level.

consuming processes

By highlighting a process, Ruxit visualizes its contribution to the overall value inside the same chart.

Which processes experience network problems?

If a network link or segment is overloaded, it will start dropping packets. This is due to the TCP protocol, which tries to retransmit the packets that have not reached its destination due to congestion and packet drop in overloaded networks.

We detect such situations and visualize them as retransmissions. Due to ruxit’s correlation algorithms, we are able to do that on host and process level.


Connectivity of processes

Independent of physical networking issues like overloaded links, processes may have their own problems with utilization and stop accepting new network connections. From a client’s perspective, this results in a timeout or in a reset of an initial TCP handshake request.

ruxit tracks such issues as “TCP connection refused” and “TCP connection timeout”. As we not only provide data but answers, we compare that to the total number of connection attempts, which gives you a short and crisp overview of your processes’ network connectivity health.


Context is everything

Numbers and metrics are nice, having them available in every relevant context is even better.

activity impact

ruxit not only displays those values on isolated detail pages, hidden beneath a plethora of other metrics. We work hard to stay true to our promise to not just deliver data, but answers. Therefore, the various problem contexts of Ruxit always display everything that’s going on at the time the problem persists.

Network monitoring in Ruxit really adds another level of value to your user experience. We provide all the data you need, where you need it, as Ruxit sports a unified user interface, that allows you to gather all the necessary information without browsing endless plugin sub-pages. Above that, Ruxit uses network domain problems as yet another potential aspect of its powerfull root cause analysis. If experience of your users is degraded due to network problems – you will know about this right away.

Your turn!

Update your agents and have a look at your network monitoring data. We are sure you’ll like the increased insight into the communication of your processes.

If you did not yet, like us on Facebook

follow us on Twitter @Dynatrace_Ruxit and @MartinGoodwell

and subscribe to our blog right here.

You think something’s still missing?

Please, let me know and I’ll hand it over to our PM department, they really appreciate a challenge, when they see one.