Client-server application monitoring

Remmon has the capability to monitor application and server performance via standard interfaces and protocols.  Remmon can also be enhanced to monitor additional fault and performance parameters using vendor provided APIs.

For client-server application monitoring (including cloud based services) we suggest a "monitor everything" approach to give the broadest range of monitoring data for comparative analysis and failure point identification. A typical Remmon monitoring solution for a client-server application will involve:

• external (to the cloud) monitoring by Remmon. This provides not only a view of public availability but also ongoing assurance that services which should be firewalled or configuration blocked are not publicly accessible;
• Remmon local agents running on servers (or virtual machines) involved in the serving the application;
• Remmon local agents running on sample client machines involved in the consuming the client-server the application;
• database monitoring through Remmon sql query execution on monitored databases.  We work with clients and application vendors to incorporate SQL queries that simulate typical application database usage;
• one or more internal Remmon monitoring instances (ReMI) within the cloud; and
• one or more Remmon monitoring appliances (ReMA) deployed on user, developer or administrator networks.  Remmon monitoring appliances can reside on particular physical or radio (Wifi, 3G, 4G etc.) networks in particular locations that represent critical data collection points for fault and performance monitoring.

Remmon fault and performance monitoring will provide:

• notifications of failure or diminished application performance.  Drill down through the monitoring levels can indicate which server or network link within the application delivery cluster is responsible for the failure or diminished performance;
• pre-emptive identification of possible failure points through Remmon local agent alerting when server resource usage (disk, memory, IO, process count etc.) exceed user defined limits;
• alerting of application access issues outside of the hosting/serving environment (through ReMA);
• alerting of database performance slow-downs (including those not related to server hardware resources).