ELM Server Architecture

The ELM family of solutions meets or exceeds requirements for monitoring today's large-scale implementations:

On the front end, ELM will monitor hundreds of machines and devices and process tens of millions of event log entries every day, gather system performance and diagnostics information, monitor application and server availability, and send real-time notification when things go wrong. In most implementations, a single ELM server will collect, evaluate, and distribute the information as it occurs. This reduces downtime, increases security, increases server and application availability, and escalates the return on investment.

ELM automation of these tasks frees your system engineers to manage more systems and to complete other pressing tasks required by today's regulatory and security demands.

On the back end, ELM will produce meaningful views of that massive amount of data. All data is securely stored in Microsoft SQL Server databases. ELM requires two database instances; the Primary Database for real-time reporting and a Failover Database to ensure data continuity should the Primary Database be unavailable. In addition, unique pruning and archiving features efficiently manage the data for long term storage needs.

ELM supports multi-tier architecture. An ELM server can forward an Alert, Event, Syslog message, or SNMP trap to another ELM server. This allows tiered system configurations or management of multiple systems in multiple locations, all at a single console. Because all communications between ELM servers is encrypted, ELM servers can be located in a DMZ, enabling real-time monitoring and notification without compromising security.

Disaster Recovery Support
ELM supports disaster recovery plans by providing an option for a Standby ELM Server in addition to the Home ELM Server. When the Home ELM Server is not available, select Service Agents assigned to a special category will automatically "swing" over and connect to a Standby ELM SErver to continue reporting functions. When the Home ELM Server is available again, the agents can be manually triggered to swing back once you determine the Home environment to be stable and ready. The Home and Standby Servers can each run their own primary database, or they could connect to the same remote database server.

The diagram below shows a high level view of the monitoring capabilities of ELM.

TNT Software's expert sales and technical staff are ready to assist you with evaluating ELM, creating requirements, and planning for implementation and deployment.

 

ELM Server and Device Monitoring Architectural Diagram