QoS Troubleshooting Tools
As well as understanding and troubleshooting the application and infrastructure, you must also understand and, if necessary, troubleshoot quality of service (QoS) settings (for example, identify whether Layer 2 switches are discarding 802.1p tags or Resource Reservation Protocol [RSVP] packets are traversing RSVP-enabled routers). The tools and methods used for network management are fundamentally different from those used for network troubleshooting. Management tools usually depend on the operation of fundamental network services, such as packet routing and Domain Name System (DNS). Troubleshooting tools are for use when things are degrading.
Network Monitoring
Network monitoring solutions, sometimes referred to as framework systems because they can monitor the delivery framework from a network perspective, have been used for many years and are designed to monitor very large, heterogeneous networks 24 x 7 to provide the following:
These solutions are used to determine system availability or to alert if performance thresholds have been exceeded.
Application Monitoring
Application-monitoring solutions vary widely in their coverage and depth. Some application monitors are designed to monitor all the interdependent parts that make up an application stack to provide event management (alerts and so forth) and store real-time and historical information. Others are designed to monitor specific parts of the application stack, often the database and network layers.
Although there is some overlap between framework and application monitoring, particularly with network and basic operating system monitoring, the purpose of application monitoring is to show availability by the following:
Application (by grouping all the pieces together) Depth of application collection Historical application performance
If a server or network connection fails, if a critical error appears in an application log, or if an object manager fails, the administrator will know which applications are affected.
| 
