Nevertheless anybody running applications in production needs to understand TCP and its basics. TCP/IP does everything in its power to makes sure that your stateful connections are reliable and perform well. Your services need not worry about retransmissions or network congestion. It knows if your service is sleeping, it knows if it’s awake, it knows if the connections run bad or good, so.

TCP, appropriate to the season, is the Santa Claus of protocols. One of the reasons this protocol stack is still around is that it’s capable of compensating for many errors on its own. Although some alternatives have been developed over the years, TCP/IP still works well and it’s the foundation of almost all networking as we know it today. The TCP/IP protocol suite that we all know so well has been around for almost 40 years now. Meanwhile, other network errors lead to performance problems that negatively affect your services.įollowing is an overview of common network errors and root causes, means and approaches of detecting such errors, and suggestions as to how monitoring tools can support you in staying on top of your services’ connectivity and performance. Some network errors are mitigated and compensated for by network protocols and active networking components, like network interfaces.

Figuring out if those errors affect the performance and connectivity of your services is however another matter. Detecting errors like dropped packets or retransmissions on the network level is relatively easy.

Wireshark filter http requests