Dependency Trees

The nectar/CMP system provides the ability to identify the relationships between interdependent technologies, events and data.  Dependency trees are the underlying system that enables this correlation and, as a result, provides the ability to determine root cause and calculate business impact.

 

When converging network topologies as in the case of Voice riding over IP and local and wide area networks, identifying and understanding the intersection points of co-existing or reliant topologies is critical in determining root cause and calculating business impact.

A core function the nectar/CMP system is the ability to identify the relationships of disparate silos of technology, events and data.  Dependency Trees are the underlying system that enables such correlation within the platform.  Dependency Trees can be automatically generated by specific VKMs and adjusted to fit actual deployment environment or manually created to illustrate in real-time complex relationships between different and dependent technologies.
Take for example a client-server web application.  The front end web server may be coupled to a back-end transaction processing system residing on a different host, while the data may sit on a SAN or network based storage facility.  Those are three (3) distinct systems each running on different hosts and reliant upon a delivery network which can consist of several elements to connect those hosts together (switches, routers, firewalls).