State of the art networking solutions are tightly coupled and proprietary in nature due to multiple vendors in the networking domain. Embodiments of the present disclosure provide a method and system for management and orchestration of heterogeneous network environment using dynamic, robust and network aware microservices. The method enables a platform for automatically and dynamically identifying appropriate group of microservices in accordance with network type and service type specified by the user, thus providing a solution that generates network aware microservices for each network in the heterogeneous network landscape. Furthermore, the system manages the identified microservices for each of the network by managing the life cycle of these microservices. The right life cycle management and coordination of the microservices for the network is in-line with desired goals/business logic, in a reliable and scalable manner, in heterogeneous network environments.

State of the art networking solutions are tightly coupled and proprietary in nature due to multiple vendors in the networking domain. Embodiments of the present disclosure provide a method and system for management and orchestration of heterogeneous network environment using dynamic, robust and network aware microservices. The method enables a platform for automatically and dynamically identifying appropriate group of microservices in accordance with network type and service type specified by the user, thus providing a solution that generates network aware microservices for each network in the heterogeneous network landscape. Furthermore, the system manages the identified microservices for each of the network by managing the life cycle of these microservices. The right life cycle management and coordination of the microservices for the network is in-line with desired goals/business logic, in a reliable and scalable manner, in heterogeneous network environments.

A device is configured to detect a triggering event within a network that is associated with a communication error between a first network device and a second network device. The device is further configured to identify a first node in a computer network map corresponding with the first network device and to identify node properties for the first node. The device is further configured to identify the error correction instructions in the node properties for the first node that include an address for rerouting data traffic to a third network device. The device is further configured to apply the error correction instructions where applying the error correction instructions suspends data traffic to the second network device and reroutes data traffic to the third network device.

Techniques for testing a networked system using simulated abnormal node failure are disclosed. In some embodiments, a computer system performs operations comprising: repeatedly transmitting simulated requests to a networked system on which a software application is implemented using a plurality of nodes, the networked system being configured to respond to the simulated requests using the plurality of nodes; randomly selecting one or more nodes from the plurality of nodes; terminating the randomly selected one or more nodes; restarting the terminated randomly selected one or more nodes; repeating the randomly selecting one or more nodes, the terminating the randomly selected one or more nodes, and the restarting the terminated randomly selected one or more nodes until each one of the plurality of nodes has been terminated and restarted at least once during the first period of time; and determining response times of the networked system in responding to the simulated requests.

This control system is provided with a controller, a controller which is a loopback communication device, a first communication route, and a second communication route. The controller generates and transmits control frames to slave devices. The controller performs loopback communication of the control frames. In the first communication route, multiple slave devices are connected between the controller and the controller using communication cables. In the second communication route, the first controller and the second controller are connected over a communication cable.

This control system is provided with a controller, a controller which is a loopback communication device, a first communication route, and a second communication route. The controller generates and transmits control frames to slave devices. The controller performs loopback communication of the control frames. In the first communication route, multiple slave devices are connected between the controller and the controller using communication cables. In the second communication route, the first controller and the second controller are connected over a communication cable.

Techniques discussed herein monitoring for and identifying failures in a cloud-computing environment. Proxy devices can be communicatively disposed between services of the cloud-computing environment. The proxy devices can capture call stack data corresponding to function calls between services. A directional graph can be generated based on that call stack data that represents the communication paths between cloud-computing resources (e.g., the services). Ingress paths to a service can be evaluated by calculating various metrics for each path. Using these metrics, failures can be isolated to a particular communication path and/or a particular, and potentially relatively distant, upstream service.

A method includes processing a user input for generating a non-deterministic finite automata tree (NFAT) correlation policy. The user input indicates one or more of a static condition or a dynamic condition for inclusion in the NFAT correlation policy. The static condition includes a comparison between a defined entity and a first fixed parameter. The dynamic condition includes a comparison between the defined entity and a variable parameter. An applicable NFAT element is generated that includes at least one of the NFAT correlation policy generated based on a determination that the user input indicates the static condition or a NFAT template generated based on a determination that the user input indicates the dynamic condition. Event data received from a network device is processed to detect a status of a network entity associated with a communication network based on the applicable NFAT element.

A method includes processing a user input for generating a non-deterministic finite automata tree (NFAT) correlation policy. The user input indicates one or more of a static condition or a dynamic condition for inclusion in the NFAT correlation policy. The static condition includes a comparison between a defined entity and a first fixed parameter. The dynamic condition includes a comparison between the defined entity and a variable parameter. An applicable NFAT element is generated that includes at least one of the NFAT correlation policy generated based on a determination that the user input indicates the static condition or a NFAT template generated based on a determination that the user input indicates the dynamic condition. Event data received from a network device is processed to detect a status of a network entity associated with a communication network based on the applicable NFAT element.

a computing system that receives and stores configuration information for the application in a data store. The configuration information comprises (1) identifiers for a plurality of cells of the application that include at least a primary cell and a secondary cell, (2) a defined state for each of the plurality of cells, (3) one or more dependencies for the application, and (4) a failover workflow defining actions to take in a failover event. The computing system receives an indication, from a customer, of a change in state of the primary cell or a request to initiate the failover event. The computing system updates, in the data store, the states for corresponding cells of the plurality of cells based on the failover workflow and updates, in the data store, the one or more dependencies for the application based on the failover workflow.