Abstract: Aspects of the subject disclosure may include, for example, identifying a network service assurance objective and obtaining first network monitoring data indicative of a first operational status of a group of network devices. The first network monitoring data are prioritized according to the network operations objective to obtain first prioritized results and a predictive model is trained based on the first network monitoring data and the first prioritized results. The second monitoring data indicative of a second operational status of the group of network devices are evaluated according to the trained predictive model to obtain second prioritized results, wherein the network monitoring data is prioritized according to the second prioritized results. Other embodiments are disclosed.

Abstract: Techniques describes herein updating pipeline flows in within data systems to maintain data integrity and consistency without manual curation. In certain embodiments, data integration system may detect and/or receive indications of a schema change within a source system of the data integration system. One or more data objects affected by the schema change may be identified, and a set of pipeline rules may be invoked for each of the affected schema changes. The pipeline rules may define a single transformation or a multi-step transformation process by which the data in the source system is provided to one or more target systems. After applying the pipeline rules to the updated source schema, the data received from the source system may be processed using the updated pipeline rules, transformed, and transmitted to the target system(s) to maintain the data integrity of the system.

Abstract: The asynchronous network inventory system provides real time and asynchronous capabilities for network applications to interact with the database of record.

Abstract: Techniques describes herein updating pipeline flows in within data systems to maintain data integrity and consistency without manual curation. In certain embodiments, data integration system may detect and/or receive indications of a schema change within a source system of the data integration system. One or more data objects affected by the schema change may be identified, and a set of pipeline rules may be invoked for each of the affected schema changes. The pipeline rules may define a single transformation or a multi-step transformation process by which the data in the source system is provided to one or more target systems. After applying the pipeline rules to the updated source schema, the data received from the source system may be processed using the updated pipeline rules, transformed, and transmitted to the target system(s) to maintain the data integrity of the system.

Abstract: In various embodiments, a data integration system is disclosed which enables users to debug distributed data integration scenarios which are platform and technology independent. A debugger client can connect to a plurality of local and/or remote hosts executing portions of a distributed data integration scenario. The debugger client can additionally enable line-by-line debugging of the portions of the distributed data integration scenario using a plurality of language-specific interfaces. The language-specific interfaces can further enable the user to dynamically update and debug changes to the code during debugging, reducing the time and resources required by multiple recompilations of the code.

Abstract: In various embodiments, a data integration system is disclosed which enables users to debug distributed data integration scenarios which are platform and technology independent. A debugger client can connect to a plurality of local and/or remote hosts executing portions of a distributed data integration scenario. The debugger client can additionally enable line-by-line debugging of the portions of the distributed data integration scenario using a plurality of language-specific interfaces. The language-specific interfaces can further enable the user to dynamically update and debug changes to the code during debugging, reducing the time and resources required by multiple recompilations of the code.

Abstract: A system and method is described for informing an upstream NMS when any changes have occurred in an electronic system architecture through a notification listener. The listener receives signals from EMS and translates them into a readily relayable format and forwards the signals to the NMS.

Abstract: A system and method is described for informing an upstream NMS when any changes have occurred in an electronic system architecture through a notification listener. The listener receives signals from EMS and translates them into a readily relayable format and forwards the signals to the NMS.

Abstract: A framework for distributed state management across servers is described, in particular for enterprise systems. The framework provides an architecture including a distributed state management adapter for servers and their applications to access a distributed state management server. The distributed state management adapter is coupled to applications through an application program interface. The distributed state management server is couple to the distributed state management adapters through a standardized service provider interface. This framework enables interoperability among applications using state data. The distributed state management system may provide or support various functionalities, including state synchronization, secure data access, event notification, state management control, transaction based state management, and persistent state back-up.