Web server:
Web servers communicate via standard Internet protocols http and https on the basis of TCP/IP. The protocol is stateless - a new connection is established for every enquiry. Possible error situations and causes are diverse and often times connected with the availability, configuration or scaling of the web server or of the applications based upon it. As a result, an enquiry can for example be rather time-consuming causing a time out or the enquiry refers to a file that is no longer existent.
File server:
File server communicate via the standard Internet protocol FTP on the basis of TCP/IP. A dedicated connection is established for each data transfer. Here too, error causes are diverse and start with the availability of the FTP service or with erroneous data transfer.
Mail server:
Many applications use SMTP protocol on the basis of TCP/IP for mail communication with a mail server. In addition to regular SMTP servers there are SMTP server that allow a secure and encrypted connection with SSL (secure SMTP server). The dispatch of a mail is compromised of connection establishment between mail client and SMTP server, login, authentication and finally of the successful mail dispatch. And at each step of this chain there is potential for disruptions and bottlenecks.
All of the above mentioned protocols pose the challenge of measuring overall availability and performance of the services adressed. Another challenge is the root cause analysis, e.g. in order to seperate errors and performance bottlenecks within applications, servers or the surrounding network.